File systems (NTFS vs EXT) CPU load bug?

[vertigo]

Has anyone tried using EXT(2/3/4) on this box?

When I inserted a freshly formatted NTFS drive in this box, I could achieve 80MB/s over the network for a very short while. So the network controller and the HDD controller are capable of these speeds. But after a few minutes, speed plummeted to 10MB/S and its been there ever since, no matter if I read or write.  This reminded me of a linux issue back in the day, when accessing NTFS drives would consume 100% CPU and make everything crawl.

I installed an android CPU monitor, and sure enough, while copying to or from the Q10, one CPU core is pegged at 100%. The others remain idle (the thread jumps between cores regularly, but its clearly a single thread using 100% of a single core). So it would seem the NTFS driver is single threaded and badly optimized, just as was the case on linux years ago.

The EXT file system should be more native to android. Is it supported? Which version ? Has anyone tried if this works and if it helps with file transfer speed? Id try it myself, but I dont have 3TB spare storage to temporarily park my video's.

[vertigo]

Correction: the cpu load only spikes when the Q10 has to read from drive, so when copying from the Q10 to somwhere else. When writing to it, I see only a modest CPU useage and the frequency remains at 400Mhz. Write speed is still only 10MB/s though.

BTW, isnt this box advertised as 2GHz quadcore? I only see 1.2GHz.

[vertigo]

And one more, major correction. Turns out my Q10 ethernet connected at 100Mbps. Used another cable, and now its at Gb speed.
Writing to the Q10 now happens at acceptable speeds, around 60MB/s. Reading from the Q10 is still too slow, 24MB/s. Likely bottlenecked by the CPU.

Since this could also affect playback, Im still interested in trying Ext4.

[futeko.com]

EXT is supported and is native to Linux/Android. It should be faster.

24MB/s is not too bad though and won't be a bottleneck for media use.