[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Benchmarking JFFS2

On Thu, May 02, 2002 at 02:40:58PM +0100, David Woodhouse wrote:

[ JFFS2 dirty fs poor performance discussd ]

> Neither of the above are valid excuses for the fact that write performance
> on a dirty file system sucks royally. There are some things we can do about
> that.

[ three optimizations suggested ]

In May I was using a prototype board running on ARM 925T (Omap). Since
then I have changed the testing to TI EVM 1510 evaluation system
available from TI. In the spring I was using 120 MHz, now 60MHz. The
flash was then 28F320B3 Strataflash chip, now it is Intel 28F128
StrataFlash. Also I am now using reasonably new snapshot of JFFS2 from
October 9th.

The performance in last spring:

Please note the block size scale is logarithmic.  Dirty files system
performance peaked at the block size of 600 .. 700 bytes and at
singular point of 4096 bytes.

The performance now with the JFFS2 snapshot from October 9th:

Please note the block size scale is linear.  The dirty file system
performance follows now very accurately to the clean file system
performance. This is partially due improved measurement accuracy:
longer benchmark time, using warmup pass, setting the benchmark do
equal mount of overwriting among data-points. The dirty file system
performance measured this way fluctuates +- 1% with 480 second
benchmark time.


This time double logarithmic chart.  I don't see over 10 second
latencies anymore. In the latency benchmark the maximum latency of
3.3s occured once among 100 000 samples.

Performance fluctuation due to GC:

The sample is short but shows the general pattern of how the background GC 
thread does its work.

Of course measuring write throughput is just one side of performance
but I think it is fair to say JFFS2 write performane on dirty file
system with low performance CPUs has improved dramatically since last

Jarkko Lavinen

To unsubscribe from this list: send the line "unsubscribe jffs-dev" in
the body of a message to majordomo@xxxxxxx.com