Hello all, Fresh install of Koha on a Debian Jessie computer. The machine has three gigs of RAM and an Athlon dual-core 4050-e. It's about 7 years old so I'm going to assume I just need a better PC, but this Koha instance (a local test server through 127.0.1.1) is so slow it's literally impossible to use, both staff and opac side. It takes about twenty seconds to resolve any request at all. Everything else on the PC is quite snappy though. Am I correct in my suspicion or is something configured incorrectly? -- View this message in context: http://koha.1045719.n5.nabble.com/Koha-glacially-slow-tp5856288.html Sent from the Koha-general mailing list archive at Nabble.com.
We're having something similar here. I upgraded to 3.20.04 last week (on Ubuntu 14.04, only running Koha) and I've heard that check in and check out are sometimes very slow. I've been out for a few days and I haven't had a chance to start investigating. Any ideas of where to start would be most welcome. Fred King Medical Librarian, MedStar Washington Hospital Center fred.king@medstar.net 202-877-6670 ORCID 0000-0001-5266-0279 Never go to a dentist with blood in his hair. --Willie Rushton -----Original Message----- From: Koha [mailto:koha-bounces@lists.katipo.co.nz] On Behalf Of Aparrish Sent: Thursday, October 08, 2015 12:23 PM To: koha@lists.katipo.co.nz Subject: [Koha] Koha glacially slow Hello all, Fresh install of Koha on a Debian Jessie computer. The machine has three gigs of RAM and an Athlon dual-core 4050-e. It's about 7 years old so I'm going to assume I just need a better PC, but this Koha instance (a local test server through 127.0.1.1) is so slow it's literally impossible to use, both staff and opac side. It takes about twenty seconds to resolve any request at all. Everything else on the PC is quite snappy though. Am I correct in my suspicion or is something configured incorrectly? -- View this message in context: http://koha.1045719.n5.nabble.com/Koha-glacially-slow-tp5856288.html Sent from the Koha-general mailing list archive at Nabble.com. _______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha MedStar Health is a not-for-profit, integrated healthcare delivery system, the largest in Maryland and the Washington, D.C., region. Nationally recognized for clinical quality in heart, orthopaedics, cancer and GI. IMPORTANT: This e-mail (including any attachments) may contain information that is private, confidential, or protected by attorney-client or other privilege. If you received this e-mail in error, please delete it from your system without copying it and notify sender by reply e-mail, so that our records can be corrected. Thank you. Help conserve valuable resources - only print this email if necessary.
Greetings, Version 3.22 is still a month or so away from release. Because from a software perspective, I think Koha running Plack is your only hope. And that will be a feature available out of the box, if I am not mistaken. However, your assumption of new hardware is a good place to start, in my opinion. https://www.cpubenchmark.net/midlow_range_cpus.html You will notice your CPU is listed near the bottom of the low to mid range CPU's. I was playing around built a junk machine on partpicker (http://pcpartpicker.com/). I was thinking an Intel G3258 or AMD FX-4300 3.8GHz Quad-Core Processor would be nice. They both hit the high range cpu page, and are relatively cheap. Anything on the high or mid-high lists would suffice. I personally don’t recommend anything lower, though if you have patience, lower is feasible to run Koha (just not well). And for the record, look at the benchmarks, Intel is rocking the list. The other thing I found unusual is 3GB or ram. A lot of motherboards are 2, 4, and if you get the really awesome boards 8 memory slots. It's usually recommended to match memory size and brand on slot pairs, particularly on Intel machines. You can take advantage of dual and quad channel memory that way. Also, given that your motherboard is likely an AM2 socket motherboard, and AMD has come out with 2 generations (AM3, AM3+) of sockets since then (and they are SLOW about that, making them a great upgrade option), I think a motherboard upgrade is in order for sure. Depending on your budget and lifecycle plans, it is possible to get away with a $500 USD machine, but more money means a nicer machine which can last longer. Debian does a stable release every 2 years. I would recommend planning a computing budget for every 4 years at worst, because 7 years ago, I would suspect your CPU was low-end of the high list maybe high-end of the mid-high list. Now it's dropped 1-2 pages. There may be some apache tweaks to speed it up, but replacing 7 year old hardware is probably a better place to start at this time. But if you can wait for 3.22, Plack may resolve your issues for less. Hope this feedback is useful. GPML, Mark Tompsett P.S. Remember database access is frequently hard drive access, unless you can cache your entire DB in memory ((1+(db backup size in GB /var/spool/koha/{instance name}/{files for same day} * 4 [because zebra is a memory hog, this might be possible with 3]) rounded up to a power of 2 -- my rough guess-timate), so an SSD might be nice. :) P.P.S. This is also why the Koha community is working on Plack as part of the default install for 3.22 (if I am not mistaken), so script running (triggering disk access) can be cached in memory (add another 1 before rounding to the equation to be safe -- another guess-timation) -----Original Message----- From: Aparrish Sent: Thursday, October 08, 2015 12:22 PM To: koha@lists.katipo.co.nz Subject: [Koha] Koha glacially slow Hello all, Fresh install of Koha on a Debian Jessie computer. The machine has three gigs of RAM and an Athlon dual-core 4050-e. It's about 7 years old so I'm going to assume I just need a better PC, but this Koha instance (a local test server through 127.0.1.1) is so slow it's literally impossible to use, both staff and opac side. It takes about twenty seconds to resolve any request at all. Everything else on the PC is quite snappy though. Am I correct in my suspicion or is something configured incorrectly?
"Version 3.22 is still a month or so away from release. Because from a software perspective, I think Koha running Plack is your only hope. And that will be a feature available out of the box, if I am not mistaken."
Really? This is fantastic. I'll hold off on troubleshooting my current Plack install in that case! You guys are outstanding. Thank you for all your hard work. I'm learning so much from this list. Best, Craig Butosi, MA, MLIS, B Mus (Hons.) LIBRARY SERVICES MANAGER THE ROYAL CONSERVATORY TELUS Centre for Performance and Learning 273 Bloor Street West Toronto, ON M5S 1W2 416.408.2824 x338 www.rcmusic.ca -----Original Message----- From: Koha [mailto:koha-bounces@lists.katipo.co.nz] On Behalf Of Mark Tompsett Sent: October-08-15 2:03 PM To: Aparrish Cc: koha@lists.katipo.co.nz Subject: Re: [Koha] Koha glacially slow Greetings, Version 3.22 is still a month or so away from release. Because from a software perspective, I think Koha running Plack is your only hope. And that will be a feature available out of the box, if I am not mistaken. However, your assumption of new hardware is a good place to start, in my opinion. https://www.cpubenchmark.net/midlow_range_cpus.html You will notice your CPU is listed near the bottom of the low to mid range CPU's. I was playing around built a junk machine on partpicker (http://pcpartpicker.com/). I was thinking an Intel G3258 or AMD FX-4300 3.8GHz Quad-Core Processor would be nice. They both hit the high range cpu page, and are relatively cheap. Anything on the high or mid-high lists would suffice. I personally don’t recommend anything lower, though if you have patience, lower is feasible to run Koha (just not well). And for the record, look at the benchmarks, Intel is rocking the list. The other thing I found unusual is 3GB or ram. A lot of motherboards are 2, 4, and if you get the really awesome boards 8 memory slots. It's usually recommended to match memory size and brand on slot pairs, particularly on Intel machines. You can take advantage of dual and quad channel memory that way. Also, given that your motherboard is likely an AM2 socket motherboard, and AMD has come out with 2 generations (AM3, AM3+) of sockets since then (and they are SLOW about that, making them a great upgrade option), I think a motherboard upgrade is in order for sure. Depending on your budget and lifecycle plans, it is possible to get away with a $500 USD machine, but more money means a nicer machine which can last longer. Debian does a stable release every 2 years. I would recommend planning a computing budget for every 4 years at worst, because 7 years ago, I would suspect your CPU was low-end of the high list maybe high-end of the mid-high list. Now it's dropped 1-2 pages. There may be some apache tweaks to speed it up, but replacing 7 year old hardware is probably a better place to start at this time. But if you can wait for 3.22, Plack may resolve your issues for less. Hope this feedback is useful. GPML, Mark Tompsett P.S. Remember database access is frequently hard drive access, unless you can cache your entire DB in memory ((1+(db backup size in GB /var/spool/koha/{instance name}/{files for same day} * 4 [because zebra is a memory hog, this might be possible with 3]) rounded up to a power of 2 -- my rough guess-timate), so an SSD might be nice. :) P.P.S. This is also why the Koha community is working on Plack as part of the default install for 3.22 (if I am not mistaken), so script running (triggering disk access) can be cached in memory (add another 1 before rounding to the equation to be safe -- another guess-timation) -----Original Message----- From: Aparrish Sent: Thursday, October 08, 2015 12:22 PM To: koha@lists.katipo.co.nz Subject: [Koha] Koha glacially slow Hello all, Fresh install of Koha on a Debian Jessie computer. The machine has three gigs of RAM and an Athlon dual-core 4050-e. It's about 7 years old so I'm going to assume I just need a better PC, but this Koha instance (a local test server through 127.0.1.1) is so slow it's literally impossible to use, both staff and opac side. It takes about twenty seconds to resolve any request at all. Everything else on the PC is quite snappy though. Am I correct in my suspicion or is something configured incorrectly? _______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha Note: This email message and any attachments are intended only for the use of the individual to which it is addressed, and may contain information that is privileged, confidential and exempt from disclosure under applicable law. If the recipient of this email is not the intended recipient (or the employee or agent responsible for delivering the email to the intended recipient), you are hereby notified that any review, dissemination, distribution or copying or other use of this message is strictly prohibited. If you have received this communication in error, please notify the sender immediately by return email and delete this message and attachments from your system, thank you.
Greetings, I wrote:
"Version 3.22 is still a month or so away from release. Because from a software perspective, I think Koha running Plack is your only hope. And that will be a feature available out of the box, if I am not mistaken."
Craig Butosi replied:
Really?
-- Really. http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13791 Status: PUSHED TO MASTER. Craig Butosi exclaimed:
This is fantastic.
-- Indeed! GPML, Mark Tompsett
Hello, 2015-10-08 19:40 GMT+01:00 Mark Tompsett <mtompset@hotmail.com>:
Greetings,
I wrote:
"Version 3.22 is still a month or so away from release. Because from a software perspective, I think Koha running Plack is your only hope. And that will be a feature available out of the box, if I am not mistaken."
Craig Butosi replied:
Really?
-- Really. http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13791 Status: PUSHED TO MASTER.
Craig Butosi exclaimed:
This is fantastic.
-- Indeed!
Which is a bit less fantastic is that our dear RM has asked for people to test the packages with Plack and did not get any answer (http://lists.koha-community.org/pipermail/koha-devel/2015-September/041811.h...). So we don't really know if it works or not. Last time a Koha running Plack has been tested in a stress session, it was not a real success as far as I know (see http://lists.koha-community.org/pipermail/koha-devel/2015-April/041375.html). So without confirmation that someone has been using it (intranet side) in production for more than 1 week without getting any problems, we cannot really say it is fantastic.
GPML, Mark Tompsett _______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
Aparrish schreef op do 08-10-2015 om 09:22 [-0700]:
but this Koha instance (a local test server through 127.0.1.1) is so slow it's literally impossible to use, both staff and opac side. It takes about twenty seconds to resolve any request at all.
What is slow? Loading the main page, performing a search, the staff interface, all of the above? When it's slow and trying to load, what is using the CPU (a command like 'top') is helpful for this. Is it apache, is it Koha Perl scripts, is it mysql, is it zebra? Or is it none of the above, in which case it might be a network configuration issue. Also keep an eye on memory use, especially to see if your machine is going into swap. On 3GB it shouldn't be, but if it is noticeably, then that would indicate something strange and would also be a problem. When it's being slow, what does the browser say? You can bring up the firefox element inspector by right-clicking on a page, and then use the network tab to get a set of graphs showing the time taken to load things, is there one thing that's slower than other things, or are they all pretty slow? You say "resolve" above, do you mean resolve in the technical sense (i.e. DNS resolution), or do you mean in the colloquial "to finish" sense? With this sort of detail, we might be able to point you towards the right place to look. -- Robin Sheat Catalyst IT Ltd. ✆ +64 4 803 2204 GPG: 5FA7 4B49 1E4D CAA4 4C38 8505 77F5 B724 F871 3BDF
Hey all, apologies for the long delay. I'm going to just respond in this thread instead of cluttering with a new one. To recap, I have an older computer running a new Koha, and I just want to make sure that there's no configuration problems before I go out and buy better hardware with my tiny budget. It is too slow to use at present. Robin - Anything and everything is slow. And I mean in the technical sense, I guess - the computer is communicating with the local server and trying to display the next page while I am waiting. The "attempting to contact..." "waiting for..." etc messages show up down in the corner. The slowdown starts as soon as I type 127.0.1.1:8080 into the browser and go. Here, this is during an invalid login request (but it's the same speed with the right data): top - 13:40:26 up 21 days, 1:17, 2 users, load average: 2.00, 1.73, 1.21 Tasks: 179 total, 8 running, 171 sleeping, 0 stopped, 0 zombie %Cpu(s): 90.5 us, 9.3 sy, 0.0 ni, 0.0 id, 0.0 wa, 0.0 hi, 0.2 si, 0.0 st KiB Mem: 3025912 total, 2820084 used, 205828 free, 210624 buffers KiB Swap: 6155260 total, 7376 used, 6147884 free. 828208 cached Mem PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 28682 www-data 20 0 358772 119388 11720 R 29.9 3.9 0:03.49 404.pl 28684 www-data 20 0 355888 116532 11692 R 29.2 3.9 0:03.26 404.pl 28686 www-data 20 0 349444 112028 11592 R 25.2 3.7 0:03.09 404.pl 28685 www-data 20 0 350104 112676 11632 R 24.6 3.7 0:03.16 404.pl 28683 www-data 20 0 358608 119188 11684 R 23.9 3.9 0:03.49 404.pl 27894 lucelib+ 20 0 1635484 489832 87084 R 20.6 16.2 11:28.66 iceweasel 2874 root 20 0 217468 34652 21428 S 7.0 1.1 16:42.25 Xorg 3119 lucelib+ 20 0 1750188 265052 57864 S 7.0 8.8 19:18.12 gnome-shell 28300 lucelib+ 20 0 411808 27092 20504 S 2.7 0.9 0:02.83 gnome-term+ 936 mysql 20 0 944440 66028 10560 S 1.7 2.2 38:00.12 mysqld 28695 www-data 20 0 24180 5800 3244 R 1.3 0.2 0:00.04 404.pl 7 root 20 0 0 0 0 S 0.3 0.0 4:08.34 rcu_sched 28477 root 20 0 23644 2848 2348 R 0.3 0.1 0:01.05 top 1 root 20 0 176152 5020 2984 S 0.0 0.2 0:32.01 systemd 2 root 20 0 0 0 0 S 0.0 0.0 0:01.74 kthreadd 3 root 20 0 0 0 0 S 0.0 0.0 13:23.84 ksoftirqd/0 5 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 kworker/0:+ Sorry, that came out very poorly formatted, but mysqld is the next highest item of interest. apache generally doesn't even make it onto this top page, nor does zebra. So I guess the top ones are Koha perl scripts then? Unfortunately I don't have firefox installed at the moment, using iceweasel, but if that data is important I'll go back and get that figured out. Also, one final thing. My Koha installation is text only. The html formatting and visual elements are all missing. Is this a problem with my installation, with the hardware requirements of the computer, or is this a setting problem with Iceweasel? I haven't gotten to compare views in different browsers yet, but I'll get on that. When I went through the graphical installer for Koha I'm pretty sure I just checked all the default options - is there a way to tell if a visual module didn't get installed? Thanks so much for all your help. -- View this message in context: http://koha.1045719.n5.nabble.com/Koha-glacially-slow-tp5856288p5860339.html Sent from the Koha-general mailing list archive at Nabble.com.
Aparrish schreef op do 05-11-2015 om 11:43 [-0700]:
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 28682 www-data 20 0 358772 119388 11720 R 29.9 3.9 0:03.49 404.pl 28684 www-data 20 0 355888 116532 11692 R 29.2 3.9 0:03.26 404.pl 28686 www-data 20 0 349444 112028 11592 R 25.2 3.7 0:03.09 404.pl 28685 www-data 20 0 350104 112676 11632 R 24.6 3.7 0:03.16 404.pl 28683 www-data 20 0 358608 119188 11684 R 23.9 3.9 0:03.49 404.pl
These 404 scripts are key.
Sorry, that came out very poorly formatted, but mysqld is the next highest item of interest. apache generally doesn't even make it onto this top page, nor does zebra. So I guess the top ones are Koha perl scripts then?
Yep.
Unfortunately I don't have firefox installed at the moment, using iceweasel, but if that data is important I'll go back and get that figured out.
Nah, that's fine.
Also, one final thing. My Koha installation is text only. The html formatting and visual elements are all missing. Is this a problem with my installation, with the hardware requirements of the computer, or is this a setting problem with Iceweasel?
This is a configuration problem, and is causing your slowdown. What is happening is that you have a path set wrong somewhere, and the browser is using that to fetch things like CSS and images. However, whenever it 404s, it launches a Perl script, and you have several 404s happening at once. If it could just deliver the file, it'd be very fast and take next to no resources, but as you have several incorrect requests going out, each one launches a script, you end up with many running at once, and things go slow. Fix your CSS and image paths, etc. and your koha will be fast again. You can get more information by using the browser's inspection thing to view network traffic and see which ones are returning 404. Ideally it should be none. -- Robin Sheat Catalyst IT Ltd. ✆ +64 4 803 2204 GPG: 5FA7 4B49 1E4D CAA4 4C38 8505 77F5 B724 F871 3BDF
participants (6)
-
Aparrish -
Craig Butosi -
Jonathan Druart -
King, Fred -
Mark Tompsett -
Robin Sheat