Re: [Koha] Checkout and other tasks takes a while
2011/2/18 Tomas Cohen Arazi <tomascohen@gmail.com>:
2011/2/18 Thommy M. Malmström <thommy.m.malmstrom@gmail.com>:
What I find is that a checkout takes 35 seconds for a single item and my question is what part of the spec is most important for better performance?
What are you calling "checkout"? You mean the process of searching for a patron, choosing him, introducing the barcode of the item and koha updating the page? Or do you mean just the barcode part?
With checkout I mean the time from I hit the button "Check Out" to the right of where I entered the bar code until the web page is updated.
2011/2/18 Thommy M. Malmström <thommy.m.malmstrom@gmail.com>:
2011/2/18 Tomas Cohen Arazi <tomascohen@gmail.com>:
2011/2/18 Thommy M. Malmström <thommy.m.malmstrom@gmail.com>:
What I find is that a checkout takes 35 seconds for a single item and my question is what part of the spec is most important for better performance?
With checkout I mean the time from I hit the button "Check Out" to the right of where I entered the bar code until the web page is updated.
Less than a second here. We have extra latency because we use an external (networked) MySQL server. I think your notebook may be using swap (then trashing) and it is probable that your MySQL is not tuned enough to have all the tables of your database in the RAM (innodb pool stuff). To+
2011/2/18 Tomas Cohen Arazi <tomascohen@gmail.com>:
2011/2/18 Thommy M. Malmström <thommy.m.malmstrom@gmail.com>:
2011/2/18 Tomas Cohen Arazi <tomascohen@gmail.com>:
2011/2/18 Thommy M. Malmström <thommy.m.malmstrom@gmail.com>:
What I find is that a checkout takes 35 seconds for a single item and my question is what part of the spec is most important for better performance?
With checkout I mean the time from I hit the button "Check Out" to the right of where I entered the bar code until the web page is updated.
Less than a second here. We have extra latency because we use an external (networked) MySQL server. I think your notebook may be using swap (then trashing) and it is probable that your MySQL is not tuned enough to have all the tables of your database in the RAM (innodb pool stuff).
Well, as it is just a test there is only 6 items in it so I think it should fit in 2 GB. If I access the DB through phpMyAdmin and change say a character in a title in the biblio table, it takes less than 1 second. So the MySQL is fast from what I can tell. It actually says "Query took 0.0001 sec". So, looks to me as if it the perl scripts, but how to tell and what to do? /Thommy M.
2011/2/18 Thommy M. Malmström <thommy.m.malmstrom@gmail.com>:
Well, as it is just a test there is only 6 items in it so I think it should fit in 2 GB.
If you don't tune your mysql it won't take advantage of your total RAM. For instance, I'm pretty sure you're running a desktop environment, a browser and an apache server on the same machine. You should see with 'top' (shift+m) how much RAM mysql is using and by the way your swap usage. Then if you use 'du' to see in /var/lib/mysql how much disk space do your databases use (you might have other databases too) and compare to the RAM the server is consuming.
If I access the DB through phpMyAdmin and change say a character in a title in the biblio table, it takes less than 1 second. So the MySQL is fast from what I can tell. It actually says "Query took 0.0001 sec". So, looks to me as if it the perl scripts, but how to tell and what to do?
You should cheeck the logs (koha-error.log). Are you using Linux, right? Try disabling things like apparmor. To+
2011/2/18 Tomas Cohen Arazi <tomascohen@gmail.com>:
2011/2/18 Thommy M. Malmström <thommy.m.malmstrom@gmail.com>:
Well, as it is just a test there is only 6 items in it so I think it should fit in 2 GB.
If you don't tune your mysql it won't take advantage of your total RAM. For instance, I'm pretty sure you're running a desktop environment, a browser and an apache server on the same machine.
Correct.
You should see with 'top' (shift+m) how much RAM mysql is using and by the way your swap usage. Then if you use 'du' to see in /var/lib/mysql how much disk space do your databases use (you might have other databases too) and compare to the RAM the server is consuming.
$ sudo du -h /var/lib/mysql 972K /var/lib/mysql/mysql 156K /var/lib/mysql/phpmyadmin 1.6M /var/lib/mysql/koha3db 39M /var/lib/mysql As shown by attached screenshot there's plenty of RAM available. I can agree that I'm low on RAM generally here, but I don't think it should have such dramatic effects. +30 seconds is hardly usable. I'll try to upgrade my SO-DIMMS to 2*2 GB...
If I access the DB through phpMyAdmin and change say a character in a title in the biblio table, it takes less than 1 second. So the MySQL is fast from what I can tell. It actually says "Query took 0.0001 sec". So, looks to me as if it the perl scripts, but how to tell and what to do?
You should cheeck the logs (koha-error.log). Are you using Linux, right? Try disabling things like apparmor.
No koha-error.log file found anywhere... Disabling apparmor speed it up by 5-10 seconds.
participants (2)
-
Thommy M. Malmström -
Tomas Cohen Arazi