Deleting buffer cache for IO throughput

by vrukesh » Fri, 29 May 2009 20:35:40 GMT

Sponsored Links

We are writing an application to measure throughput speed of SD card
on ARM-based Android target using Java APIs.

When we execute the application twice for read operation, results are
seen to be affected with buffer cache.

For example, first read throughput is 275 KBps and second read
throughput is 350KBps.

Application is simple Java-based application, it is .jar app. It is
not using the Application class  and hence, not having
AndroidManifest.xml present. ().

Is there any way to clear the buffer cache after each run of the
application ?

Thanks and Regards,

Other Threads

1. Mod: Gathering ID-Android with HTC Indonesia (Sabtu, 26 Juni 2010)

Wah om agus, berarti buat kita2 para pengguna HTC dapet freebies dung?
asikkkk, mbahnya htc android mustinya dapet extra bonus nie ^^

*harap2 ngayal

oys will always be Dreamrs

2010/6/18 Agus Hamonangan <>


2. Background apps (Instant Messaging) being killed without user notification


I think this should be taken up with developers of these apps.

In particular, my recommendations to them would be:

- Use a startForeground / setForeground call to mark the service as being important to the user, do it only while the user is logged in. - Display a notification the phone's status bar, so the user knows if the service is still kicked out of memory. - Consider using AlarmManager to restart the service and re-login if there is an active logged in session. -- Kostya 23.06.2010 20:07, Simon Broenner :
1. Why am I, the user, not informed the the application has died, and hence, the connection has been lost? 2. Why are all the IM apps being killed, and not my other background apps? Sipdroid and Locale have NEVER been killed in this fashion.
-- Kostya Vasilev -- WiFi Manager + pretty widget -- --

3. Background apps (Instant Messaging) being killed without user notification

4. Google support number for Droid's sent to Developers from Google?

5. Preorder samsung galaxy spica s

6. AlarmManager ceasing to function. Dropping single shot alarms.

7. Auto-completion/correction hints