At 07:07 AM 8/2/2011 -0400, Ian Walls wrote:
ByWater Solutions also runs 64 bit Debian Squeeze, and we are quite pleased with it.
Tnx to all for your replies. A follow-up if I may? How much RAM are you using? My current "sand-box server" is very slow (4-7 seconds for searches, admin saves, etc) with only 2 gigs; we are refining our new specs and hesitating between 8 and 16 gigs for the new box. Our users and cataloguers are really looking for more or less instantaneous responses to OPAC searches and I'm looking for all the hardware design help I can get. Best regards - Paul
-Ian
On Mon, Aug 1, 2011 at 9:57 PM, Paul Poulain <<mailto:paul.poulain@biblibre.com>paul.poulain@biblibre.com> wrote: Le 01/08/2011 23:07, Chris Cormack a écrit :
I'll then migrate our current db from 3.2 (on a 32-bit machine) and again would appreciate any words of wisdom from any of you as to best practices. Â The new server will use Ubuntu 10.04LTS rather than 10.10 (current server) just for the long-term maintenance schedule in a production environment.
We run our production systems on 64bit debian squeeze, with no issues Same thing for us: 64bits debian squeeze, with no issues
Paul Tired old sys-admin
Paul <paul.a@aandc.org> writes:
Tnx to all for your replies. A follow-up if I may? How much RAM are you using? My current "sand-box server" is very slow (4-7 seconds for searches, admin saves, etc) with only 2 gigs; we are refining our new specs and hesitating between 8 and 16 gigs for the new box. Our users and cataloguers are really looking for more or less instantaneous responses to OPAC searches and I'm looking for all the hardware design help I can get.
1gig ram <tries to hide> for a 7.2K volumes library. Not exactly instantaneous responses, but neither so slow. 3.4.2 is visibly faster than 3.4.1 anyway - especially in staff client searches. -- Mahesh T. Pai || Half knowledge is worse than ignorance. --Thomas B. Macaulay
Le 02/08/2011 17:00, Mahesh T Pai a écrit :
3.4.2 is visibly faster than 3.4.1 anyway - especially in staff client searches. really ? anyone has a technical explanation to this boost ?
-- Paul POULAIN http://www.biblibre.com Expert en Logiciels Libres pour l'info-doc Tel : (33) 4 91 81 35 08
El , Paul Poulain <paul.poulain@biblibre.com> escribió:
Le 02/08/2011 17:00, Mahesh T Pai a écrit :
3.4.2 is visibly faster than 3.4.1 anyway - especially in staff client
searches.
really ? anyone has a technical explanation to this boost ?
Maybe they've just installed memcached which they didn't when installing 3.4.1 Regards To+
The guideline we've followed is to have as much RAM as you do MySQL database. For a very large system, that's not always possible, and isn't even necessary with the right tuning, but RAM more than anything is the key resource to throw at Koha for snappier response. -Ian 2011/8/2 Paul <paul.a@aandc.org>
At 07:07 AM 8/2/2011 -0400, Ian Walls wrote:
ByWater Solutions also runs 64 bit Debian Squeeze, and we are quite pleased with it.
Tnx to all for your replies. A follow-up if I may? How much RAM are you using? My current "sand-box server" is very slow (4-7 seconds for searches, admin saves, etc) with only 2 gigs; we are refining our new specs and hesitating between 8 and 16 gigs for the new box. Our users and cataloguers are really looking for more or less instantaneous responses to OPAC searches and I'm looking for all the hardware design help I can get.
Best regards - Paul
-Ian
I'll then migrate our current db from 3.2 (on a 32-bit machine) and again would appreciate any words of wisdom from any of you as to best
On Mon, Aug 1, 2011 at 9:57 PM, Paul Poulain <paul.poulain@biblibre.com> wrote: Le 01/08/2011 23:07, Chris Cormack a écrit : practices.
 The new server will use Ubuntu 10.04LTS rather than 10.10 (current server)
just for the long-term maintenance schedule in a production environment.
We run our production systems on 64bit debian squeeze, with no issues Same thing for us: 64bits debian squeeze, with no issues
**
** Paul Tired old sys-admin
_______________________________________________ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
-- Ian Walls Lead Development Specialist ByWater Solutions Phone # (888) 900-8944 http://bywatersolutions.com ian.walls@bywatersolutions.com Twitter: @sekjal
Le 02/08/2011 18:36, Ian Walls a écrit :
The guideline we've followed is to have as much RAM as you do MySQL database. For a very large system, that's not always possible, and isn't even necessary with the right tuning, but RAM more than anything is the key resource to throw at Koha for snappier response.
good point Ian. Paul, you can look at http://www.biblibre.com/en/blog/entry/mysql-default-config-and-very-large-ko... to see which configuration we use. -- Paul POULAIN http://www.biblibre.com Expert en Logiciels Libres pour l'info-doc Tel : (33) 4 91 81 35 08
participants (5)
-
Ian Walls -
Mahesh T Pai -
Paul -
Paul Poulain -
tomascohen＠gmail.com