<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=UTF-8" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
<br>
<blockquote
cite="mid:b1335fe90905161154j16666bf8vc39fff04213f6abb@mail.gmail.com"
type="cite">
<div class="gmail_quote">
<div><br>
Sorry, should have explained myself better, as I was also talking about
memory speed and not size, this time.<br>
</div>
</div>
</blockquote>
Ahh, if you wrote about memory size then never mind my comments. :)<br>
<blockquote
cite="mid:b1335fe90905161154j16666bf8vc39fff04213f6abb@mail.gmail.com"
type="cite">
<div class="gmail_quote">
<div><br>
Thing is, most flash controller implementations are crap, and it will
probably be the case with the one in Gen 1.5. I'm quoting 0.5MB/s in <b>random
writes</b> to the file system, nothing to do with compression. Most
decent SSDs can write at last 1MB/s with some topping 2MB/s, in random
patterns, sequential is about 150MB/s+. Sequential is not the problem
when using SD cards or most USB drives, random writes is, when you're
trying to have an OS on it. <br>
The best drives around, from Intel, can do 20+MB/s in random writes.<br>
<br>
</div>
</div>
</blockquote>
<blockquote
cite="mid:b1335fe90905161154j16666bf8vc39fff04213f6abb@mail.gmail.com"
type="cite">
<div class="gmail_quote">
<div>Most SSDs on the market are based on J-Micron controllers that
can do, at most, 0.04MB/s in random writes. This causes the system to
frequently stall when some app is performing heavy writes to arbitrary
locations. Random reads are mostly very fast with every type of flash
you can get.<br>
<br>
<a moz-do-not-send="true"
href="http://www.anandtech.com/storage/showdoc.aspx?i=3531&p=25">http://www.anandtech.com/storage/showdoc.aspx?i=3531&p=25</a><br>
<br>
0.5MB/s in RR should be enough to avoid most stalls.<br>
<br>
</div>
</div>
</blockquote>
I hope that Mich Bradley will educate us but it seems to me that the
hidden eraseblock handling can be the problem with those devices (and
if it is true then compression will not help it either). It seems to be
that some tests are required with physical hardware, a paper processor
will not be enough... :)<br>
<br>
Are there any plans using UBIFS?<br>
<br>
</body>
</html>