Just an update,
I have installed a new ext4 volume on the server and moved basex data over to it. Updates are now fast, so there was definitely an improvement. I will wait to see it running for a whole day before I draw conclusions, but I wasn't able to reproduce my high-io kjournald problem (or any other similar problem) with the data on ext4.
- Adrian
On Sat, Jan 7, 2012 at 1:33 AM, Adrian Hossu adibadi@gmail.com wrote:
Hi all,
I'm been running basex on two environments, one is my laptop with an SSD drive and ext4, the other is a server with raid-1 HDD and ext3.
Using iotop, I am watching the disk access of the server and laptop, and comparing the two.
After some update queries, I notice that the server (ext3) has a process, [kjournald], which writes for about 20 seconds at 600-1000KB/sec. This only begins after the update is complete and the java process actually stops writing. I am not experiencing such a thing on my laptop. If I do too many of these queries on the server, it will eventually hang for 20-30 seconds.
I've copied the exact data on both the laptop and the server.
Are there any recommended filesystem types for basex? Does it sound like I've configured something incorrectly, or should I add some more drives to my server and have them using ext4? Or is the difference SSD vs HDD? I never saw my SSD write speed go above 200KB/sec or so during the same queries.
Any help would be greatly appreciated!
- Adrian