Re: [Koha] Koha performance and 6 million records

[Michael Kuhn]

Hi Ere

Many thanks for your thoughts and technical tips!

For the moment the library decided not to load their 6 million records 
into Koha (with Zebra) but to index them separately, either in Vufind or 
in ALBERT (a discovery system developed by the KOBV, a German union 
catalog) which like Elasticsearch all are using Solr Lucene. The main 
reason for the decision is the actual development status Koha using 
Elasticsearch.


However, this will probably be reconsiderated one day in the future when 
Elasticsearch is fully integrated into Koha, all/most bugs omitted, and 
when Zebra definitely will be gone.


Best wishes: Michael
--
Geschäftsführer · Diplombibliothekar BBS, Informatiker eidg. Fachausweis
Admin Kuhn GmbH · Pappelstrasse 20 · 4123 Allschwil · Schweiz
T 0041 (0)61 261 55 61 · E m...@adminkuhn.ch · W www.adminkuhn.ch
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Koha performance and 6 million records

[Ere Maijala]

Hi,

In my experience such fairly large setup is not worth doing with Zebra,
but should be no problem with Elasticsearch. However, whenever there are
questions on performance, most answers would be guesswork apart from
"try it and see how it goes".

For what it's worth, here are my thoughts:

- Use Elasticsearch for a large index. It's faster and uses a lot less
disk space. It can also be moved to a separate host if necessary.

- Faster disk always helps, and even if performance would be adequate
otherwise, fast disk makes many tasks more comfortable to execute.

- With Elasticsearch (and MariaDB to some extent), need to make sure
there's enough memory allocated for them. With 6 million records you may
need to increase the heap reserved for ES, but more important is to have
enough free memory on the server that enough or all of the index can be
cached in memory.

- Having separate host for e.g. Elasticsearch but maybe also MariaDB
makes it easier to manage their resources and make sure that one of them
doesn't hog resources from the others.

- A separate discovery service allows you to separate search load
between staff use and patron use, but you may end up needing double the
resources to run the complete system. Obviously a separate system allows
other flexibility too, but comes with more complex setup.

- Note that while Elasticsearch now works pretty well, there are still
some open issues, and every new Koha release has things improved. I'd
run tests with the latest master version if possible. You may also be
interested in enhancements still in the pipeline, such as parallelizing
the indexing process:
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21872

As you can see from the above points, I'd consider the search index the
critical part for good performance. Obviously it's also necessary to
make sure MariaDB, Plack etc. get enough resources, but I'd still say
that the search index is the one that makes or breaks it.

Regards,
Ere

Michael Kuhn kirjoitti 3.3.2019 klo 13.15:
> Hi
> 
> We are currently running Koha 18.11 on Debian GNU/Linux 9 (virtual
> machine with 2 processors, 4 GB RAM) and 50'000 bibliographic records in
> a MariaDB database, using Zebra, and of course Plack and Memcached.
> There are only about 160 users. We would like to add 6 million
> bibliographic records (metadata of articles) that before were only
> indexed in the Solr index of a proprietary discovery system, but not in
> Koha itself.
> 
> Since we are lacking experience in such large masses of data we would
> like to investigate about the consequences:
> 
> * Will the overall performance and especially the retrieval experience
> suffer a lot? (note there are only 160 users) We're afraid it will...
> 
> * If yes, is there a way to improve the retrieval experience? For
> example changing from a virtual machine to a dedicated or physical host?
> Adding more resp. faster processors, more RAM? Using SSD disks instead
> of SAS? Changing from Zebra to Elasticsearch? Or will we need to
> implement another discovery system, like Vufind (which is using Solr
> Energy)?
> 
> Any tips or hints are very much appreciated!
> 
> Best wishes: Michael

-- 
Ere Maijala
Kansalliskirjasto / The National Library of Finland
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Koha Performance

[JanM]

Oh man! I promis you will get invited for those cookies i we should meet us
one day. Thanks, that worked.



--
Sent from: http://koha.1045719.n5.nabble.com/Koha-general-f3047918.html
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Koha Performance

[Tomas Cohen Arazi]

And I like hazelnut cookies, BTW :-D

El mar., 20 mar. 2018 a las 11:35, Tomas Cohen Arazi ()
escribió:

> The best thing you could do, is regenerate the instance with sane clean
> apache configuration files, and import the DB to the fresh instance. This
> way, you will get your apache files patched on each upgrade, etc. This
> hand-made files will cause you trouble in the future.
>
> A workaround for your situation exists, though. Add the following line:
>
> Define instance "library"
>
> right below each '
>
>
> El mar., 20 mar. 2018 a las 11:29, JanM ()
> escribió:
>
>> No LSB modules are available.
>> Distributor ID: Ubuntu
>> Description:Ubuntu 16.04.4 LTS
>> Release:16.04
>> Codename:   xenial
>>
>> Koha-Version: 17.11.03.000
>>
>> Perl-Version: 5.022001
>>
>> Apache-Version: Server version: Apache/2.4.18 (Ubuntu)
>>
>> MySQL-Version: mysql Ver 15.1 Distrib 10.0.34-MariaDB, for
>> debian-linux-gnu
>>
>>
>>
>> --
>> Sent from: http://koha.1045719.n5.nabble.com/Koha-general-f3047918.html
>> ___
>> Koha mailing list  http://koha-community.org
>> Koha@lists.katipo.co.nz
>> https://lists.katipo.co.nz/mailman/listinfo/koha
>>
> --
> Tomás Cohen Arazi
> Theke Solutions (https://theke.io )
> ✆ +54 9351 3513384 <+54%209%20351%20351-3384>
> GPG: B2F3C15F
>
-- 
Tomás Cohen Arazi
Theke Solutions (https://theke.io )
✆ +54 9351 3513384
GPG: B2F3C15F
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Koha Performance

[Tomas Cohen Arazi]

The best thing you could do, is regenerate the instance with sane clean
apache configuration files, and import the DB to the fresh instance. This
way, you will get your apache files patched on each upgrade, etc. This
hand-made files will cause you trouble in the future.

A workaround for your situation exists, though. Add the following line:

Define instance "library"

right below each ')
escribió:

> No LSB modules are available.
> Distributor ID: Ubuntu
> Description:Ubuntu 16.04.4 LTS
> Release:16.04
> Codename:   xenial
>
> Koha-Version: 17.11.03.000
>
> Perl-Version: 5.022001
>
> Apache-Version: Server version: Apache/2.4.18 (Ubuntu)
>
> MySQL-Version: mysql Ver 15.1 Distrib 10.0.34-MariaDB, for debian-linux-gnu
>
>
>
> --
> Sent from: http://koha.1045719.n5.nabble.com/Koha-general-f3047918.html
> ___
> Koha mailing list  http://koha-community.org
> Koha@lists.katipo.co.nz
> https://lists.katipo.co.nz/mailman/listinfo/koha
>
-- 
Tomás Cohen Arazi
Theke Solutions (https://theke.io )
✆ +54 9351 3513384
GPG: B2F3C15F
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Koha Performance

[JanM]

No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 16.04.4 LTS
Release:16.04
Codename:   xenial

Koha-Version: 17.11.03.000

Perl-Version: 5.022001 

Apache-Version: Server version: Apache/2.4.18 (Ubuntu) 

MySQL-Version: mysql Ver 15.1 Distrib 10.0.34-MariaDB, for debian-linux-gnu 



--
Sent from: http://koha.1045719.n5.nabble.com/Koha-general-f3047918.html
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Koha Performance

[Tomas Cohen Arazi]

What is the OS version?

El mar., 20 mar. 2018 a las 11:24, JanM ()
escribió:

> Ok, done that. After restarting the Apache it says:
>
> /Service Unavailable
>
> The server is temporarily unable to service your request due to maintenance
> downtime or capacity problems. Please try again later./
>
> in the Webbrowser.
>
> Restart worked without errors. Also tried koha-plack --restart library
> without errors
>
>
>
> --
> Sent from: http://koha.1045719.n5.nabble.com/Koha-general-f3047918.html
> ___
> Koha mailing list  http://koha-community.org
> Koha@lists.katipo.co.nz
> https://lists.katipo.co.nz/mailman/listinfo/koha
>
-- 
Tomás Cohen Arazi
Theke Solutions (https://theke.io )
✆ +54 9351 3513384
GPG: B2F3C15F
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Koha Performance

[JanM]

Ok, done that. After restarting the Apache it says:

/Service Unavailable

The server is temporarily unable to service your request due to maintenance
downtime or capacity problems. Please try again later./

in the Webbrowser.

Restart worked without errors. Also tried koha-plack --restart library
without errors



--
Sent from: http://koha.1045719.n5.nabble.com/Koha-general-f3047918.html
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Koha Performance

[Tomas Cohen Arazi]

Right, that's what I thought.

You need to add the following:

 Include /etc/koha/apache-shared-opac-plack.conf

above the line that says:

 Include /etc/koha/apache-shared-opac.conf

And

 Include /etc/koha/apache-shared-intranet-plack.conf

above the line that says:

 Include /etc/koha/apache-shared-intranet.conf

Then restart the apache2 service, again.



El mar., 20 mar. 2018 a las 11:03, JanM ()
escribió:

> Ok, gotcha.. I have two files, first:
>
> 
>
>
> 
>
>Include /etc/koha/apache-shared.conf
> #  Include /etc/koha/apache-shared-disable.conf
>Include /etc/koha/apache-shared-opac.conf
>
>SSLCertificateFile /etc/ssl/certs/.pem
>SSLCertificateKeyFile /etc/ssl/private/.pem
>SSLCertificateChainFile /etc/ssl/ca.crt
>
>ServerName myservername
>
>SetEnv KOHA_CONF "/etc/koha/sites/library/koha-conf.xml"
>SetEnv MEMCACHED_SERVERS ""
>SetEnv MEMCACHED_NAMESPACE ""
>AssignUserID library-koha library-koha
>
>ErrorLog/var/log/koha/library/opac-error.log
> #  TransferLog /var/log/koha/library/opac-access.log
> #  RewriteLog  /var/log/koha/library/opac-rewrite.log
>
>
>
> ServerAdmin x...@xxx.de
>
> ErrorLog ${APACHE_LOG_DIR}/error.log
>
> # Possible values include: debug, info, notice, warn, error, crit,
> # alert, emerg.
> LogLevel warn
>
> CustomLog ${APACHE_LOG_DIR}/ssl_access.log combined
> #   SSL Engine Switch:
> #   Enable/Disable SSL for this virtual host.
> SSLEngine on
>
> 
> SSLOptions +StdEnvVars
> 
> 
> SSLOptions +StdEnvVars
> 
>
> BrowserMatch "MSIE [2-6]" \
> nokeepalive ssl-unclean-shutdown \
> downgrade-1.0 force-response-1.0
> # MSIE 7 and newer should be able to use keepalive
> BrowserMatch "MSIE [17-9]" ssl-unclean-shutdown
>
>
>
> 
>
> 
>
>
> second:
>
> 
>
>
> 
>
>SSLCertificateFile /etc/ssl/certs/.pem
>SSLCertificateKeyFile /etc/ssl/private/.pem
>SSLCertificateChainFile /etc/ssl/ca.crt
>
>Include /etc/koha/apache-shared.conf
> #  Include /etc/koha/apache-shared-disable.conf
>Include /etc/koha/apache-shared-intranet.conf
>
>ServerName myservername
>
>SetEnv KOHA_CONF "/etc/koha/sites/library/koha-conf.xml"
>SetEnv MEMCACHED_SERVERS ""
>SetEnv MEMCACHED_NAMESPACE ""
>AssignUserID library-koha library-koha
>
>ErrorLog/var/log/koha/library/opac-error.log
> #  TransferLog /var/log/koha/library/opac-access.log
> #  RewriteLog  /var/log/koha/library/opac-rewrite.log
>
>
>
> ServerAdmin x...@xxx.de
>
> ErrorLog ${APACHE_LOG_DIR}/error.log
>
> # Possible values include: debug, info, notice, warn, error, crit,
> # alert, emerg.
> LogLevel warn
>
> CustomLog ${APACHE_LOG_DIR}/ssl_access.log combined
> #   SSL Engine Switch:
> #   Enable/Disable SSL for this virtual host.
> SSLEngine on
>
> 
> SSLOptions +StdEnvVars
> 
> 
> SSLOptions +StdEnvVars
> 
>
> BrowserMatch "MSIE [2-6]" \
> nokeepalive ssl-unclean-shutdown \
> downgrade-1.0 force-response-1.0
> # MSIE 7 and newer should be able to use keepalive
> BrowserMatch "MSIE [17-9]" ssl-unclean-shutdown
> 
>
> 
>
>
>
>
> --
> Sent from: http://koha.1045719.n5.nabble.com/Koha-general-f3047918.html
> ___
> Koha mailing list  http://koha-community.org
> Koha@lists.katipo.co.nz
> https://lists.katipo.co.nz/mailman/listinfo/koha
>
-- 
Tomás Cohen Arazi
Theke Solutions (https://theke.io )
✆ +54 9351 3513384
GPG: B2F3C15F
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Koha Performance

[JanM]

Ok, gotcha.. I have two files, first:






   Include /etc/koha/apache-shared.conf
#  Include /etc/koha/apache-shared-disable.conf
   Include /etc/koha/apache-shared-opac.conf

   SSLCertificateFile /etc/ssl/certs/.pem
   SSLCertificateKeyFile /etc/ssl/private/.pem
   SSLCertificateChainFile /etc/ssl/ca.crt

   ServerName myservername 

   SetEnv KOHA_CONF "/etc/koha/sites/library/koha-conf.xml"
   SetEnv MEMCACHED_SERVERS ""
   SetEnv MEMCACHED_NAMESPACE ""
   AssignUserID library-koha library-koha

   ErrorLog/var/log/koha/library/opac-error.log
#  TransferLog /var/log/koha/library/opac-access.log
#  RewriteLog  /var/log/koha/library/opac-rewrite.log



ServerAdmin x...@xxx.de

ErrorLog ${APACHE_LOG_DIR}/error.log

# Possible values include: debug, info, notice, warn, error, crit,
# alert, emerg.
LogLevel warn

CustomLog ${APACHE_LOG_DIR}/ssl_access.log combined
#   SSL Engine Switch:
#   Enable/Disable SSL for this virtual host.
SSLEngine on


SSLOptions +StdEnvVars


SSLOptions +StdEnvVars


BrowserMatch "MSIE [2-6]" \
nokeepalive ssl-unclean-shutdown \
downgrade-1.0 force-response-1.0
# MSIE 7 and newer should be able to use keepalive
BrowserMatch "MSIE [17-9]" ssl-unclean-shutdown








second:






   SSLCertificateFile /etc/ssl/certs/.pem
   SSLCertificateKeyFile /etc/ssl/private/.pem
   SSLCertificateChainFile /etc/ssl/ca.crt

   Include /etc/koha/apache-shared.conf
#  Include /etc/koha/apache-shared-disable.conf
   Include /etc/koha/apache-shared-intranet.conf

   ServerName myservername 

   SetEnv KOHA_CONF "/etc/koha/sites/library/koha-conf.xml"
   SetEnv MEMCACHED_SERVERS ""
   SetEnv MEMCACHED_NAMESPACE ""
   AssignUserID library-koha library-koha

   ErrorLog/var/log/koha/library/opac-error.log
#  TransferLog /var/log/koha/library/opac-access.log
#  RewriteLog  /var/log/koha/library/opac-rewrite.log



ServerAdmin x...@xxx.de

ErrorLog ${APACHE_LOG_DIR}/error.log

# Possible values include: debug, info, notice, warn, error, crit,
# alert, emerg.
LogLevel warn

CustomLog ${APACHE_LOG_DIR}/ssl_access.log combined
#   SSL Engine Switch:
#   Enable/Disable SSL for this virtual host.
SSLEngine on


SSLOptions +StdEnvVars


SSLOptions +StdEnvVars


BrowserMatch "MSIE [2-6]" \
nokeepalive ssl-unclean-shutdown \
downgrade-1.0 force-response-1.0
# MSIE 7 and newer should be able to use keepalive
BrowserMatch "MSIE [17-9]" ssl-unclean-shutdown







--
Sent from: http://koha.1045719.n5.nabble.com/Koha-general-f3047918.html
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Koha Performance

[Tomas Cohen Arazi]

Your eyes are on the :80 entry, but that entry redirects to another vhost
definition, using port 443. You need to look at the 443 vhost definition
for answers, as the port 80 one doesn't actually *server* Koha, it just
redirects.

El mar., 20 mar. 2018 a las 10:48, JanM ()
escribió:

> I think it is a custom made file, but I don't know. I was asked to
> administrate the server since the guy before me has left us.
> What is important about the redirect? Is it the entry causing the fault?
> Should it be deleted? Or should it be there, like without it, it would not
> work.
>
>
>
> --
> Sent from: http://koha.1045719.n5.nabble.com/Koha-general-f3047918.html
> ___
> Koha mailing list  http://koha-community.org
> Koha@lists.katipo.co.nz
> https://lists.katipo.co.nz/mailman/listinfo/koha
>
-- 
Tomás Cohen Arazi
Theke Solutions (https://theke.io )
✆ +54 9351 3513384
GPG: B2F3C15F
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Koha Performance

[JanM]

I think it is a custom made file, but I don't know. I was asked to
administrate the server since the guy before me has left us. 
What is important about the redirect? Is it the entry causing the fault?
Should it be deleted? Or should it be there, like without it, it would not
work.



--
Sent from: http://koha.1045719.n5.nabble.com/Koha-general-f3047918.html
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Koha Performance

[Tomas Cohen Arazi]

The important entry is the one for port 443. This one only does a redirect.
Is that generated by koha-create or a custom made apache file?

El mar., 20 mar. 2018 a las 10:18, JanM ()
escribió:

> This is the apache conf file that we use. Maybe someone can give a hint or
> something, 'cause i'm running out of ideas. The "koha-plack --enable" does
> not seem to do anything. If I run the disable command there are # placed in
> front of the include. After enable the plack and restarting the apache
> these
> are gone, but nothing changed. I don't know the default configuration of
> this file or any other file, pls someone help.
>
> 
>   Define instance library
>   Include /etc/koha/apache-shared-opac-plack.conf
>   ServerName www2.testothek.uni-hamburg.de:80
>   Redirect / https://www2.testothek.uni-hamburg.de:443
> 
>
>
>
>
>
>
>
>
> --
> Sent from: http://koha.1045719.n5.nabble.com/Koha-general-f3047918.html
> ___
> Koha mailing list  http://koha-community.org
> Koha@lists.katipo.co.nz
> https://lists.katipo.co.nz/mailman/listinfo/koha
>
-- 
Tomás Cohen Arazi
Theke Solutions (https://theke.io )
✆ +54 9351 3513384
GPG: B2F3C15F
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Koha Performance

[JanM]

This is the apache conf file that we use. Maybe someone can give a hint or
something, 'cause i'm running out of ideas. The "koha-plack --enable" does
not seem to do anything. If I run the disable command there are # placed in
front of the include. After enable the plack and restarting the apache these
are gone, but nothing changed. I don't know the default configuration of
this file or any other file, pls someone help. 


  Define instance library
  Include /etc/koha/apache-shared-opac-plack.conf
  ServerName www2.testothek.uni-hamburg.de:80
  Redirect / https://www2.testothek.uni-hamburg.de:443









--
Sent from: http://koha.1045719.n5.nabble.com/Koha-general-f3047918.html
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Koha Performance

[Mark Alexander]

Excerpts from Narcis Garcia's message of 2018-03-20 10:38:26 +0100:
> 1. What is the concrete indicator that Plack is enabled and running or not?

In the "About Koha" page, immediately after the "Apache version:" line, you 
should
see a line that looks like this:

PSGI:   Plack (deployment)
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Koha Performance

[Narcis Garcia]

Two questions about Plack:

1. What is the concrete indicator that Plack is enabled and running or not?

2. I've looked at https://wiki.koha-community.org/wiki/Plack but: What
can be useful for plack in my setup or for me?
Recommended? Required? Extra? Only for developers?

Thank you.


El 19/03/18 a les 17:34, Tomas Cohen Arazi ha escrit:
> El lun., 19 mar. 2018 a las 11:35, JanM ()
> escribió:
> 
>> MySQL-Version:  mysql Ver 15.1 Distrib 10.0.34-MariaDB, for
>> debian-linux-gnu
>> (x86_64) using readline 5.2
>> Apache-Version: Server version: Apache/2.4.18 (Ubuntu)
>> Memcached:  Server: Nicht definiert | Namespace: koha | Status:
>> unbekannt |
>> Konfiguration gelesen aus: Nirgendwo Bitte beachten Sie, dass die
>> Memcached-Konfiguration in Iher $KOHA_CONF-Datei erfolgen sollte. Aktuell
>> gibt es keine gültige Memcached-Konfiguration. | Aktive Caching-Methode:
>> Cache::Memory/
>>
> 
> You are not running Plack (or is not configured correctly. To enable it you
> need to run:
> 
>  $ sudo koha-plack --enable 
>  $ sudo koha-plack --restart 
>  $ sudo systemctl restart apache2
> 
> If it is already enabled, chances are you havent restarted apache2 or
> launched the koha-plack process.
> 
> Good luck!
> 
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Koha Performance

[JanM]

root@www2:/home/user# koha-plack --enable library
Plack enabled for library
root@www2:/home/user# koha-plack --restart library
* Restarting Plack daemon for library   
 
* Stopping Plack daemon for library 

[ OK ]
* Starting Plack daemon for library 

[ OK ]

 
[ OK ]
root@www2:/home/user# systemctl restart apache2


Tried your steps accordingly but with no performance gain. The About Page
now says:

Serverinformationen Koha-Version:   17.11.03.000
OS Version ('uname -a'):Linux www2 4.4.0-96-generic #119-Ubuntu SMP Tue
Sep 12 14:59:54 UTC 2017 x86_64
Perl Interpreter:   /usr/bin/perl
Perl-Version:   5.022001
Perl @INC:  /usr/share/koha/lib
/etc/perl
/usr/local/lib/x86_64-linux-gnu/perl/5.22.1
/usr/local/share/perl/5.22.1
/usr/lib/x86_64-linux-gnu/perl5/5.22
/usr/share/perl5
/usr/lib/x86_64-linux-gnu/perl/5.22
/usr/share/perl/5.22
/usr/local/lib/site_perl
/usr/lib/x86_64-linux-gnu/perl-base
.
MySQL-Version:  mysql Ver 15.1 Distrib 10.0.34-MariaDB, for debian-linux-gnu
(x86_64) using readline 5.2
Apache-Version: Server version: Apache/2.4.18 (Ubuntu)
Memcached:  Server: 127.0.0.1:11211 | Namespace: koha | Status: wird
ausgeführt. | Konfiguration gelesen aus: koha-conf.xml
Zebraversion:   Zebra 2.0.59 (C) 1994-2014, Index Data Zebra is free
software, covered by the GNU General Public License, and you are welcome to
change it and/or distribute copies of it under certain conditions. SHA1 ID:
c00bfddbf0f3608340d61298acc61dafb167f9b2 Using ICU 

Where do you see that Plack is not running? Should it say so in the "Perl
@INC"? 




--
Sent from: http://koha.1045719.n5.nabble.com/Koha-general-f3047918.html
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Koha Performance

[Tomas Cohen Arazi]

El lun., 19 mar. 2018 a las 11:35, JanM ()
escribió:

> MySQL-Version:  mysql Ver 15.1 Distrib 10.0.34-MariaDB, for
> debian-linux-gnu
> (x86_64) using readline 5.2
> Apache-Version: Server version: Apache/2.4.18 (Ubuntu)
> Memcached:  Server: Nicht definiert | Namespace: koha | Status:
> unbekannt |
> Konfiguration gelesen aus: Nirgendwo Bitte beachten Sie, dass die
> Memcached-Konfiguration in Iher $KOHA_CONF-Datei erfolgen sollte. Aktuell
> gibt es keine gültige Memcached-Konfiguration. | Aktive Caching-Methode:
> Cache::Memory/
>

You are not running Plack (or is not configured correctly. To enable it you
need to run:

 $ sudo koha-plack --enable 
 $ sudo koha-plack --restart 
 $ sudo systemctl restart apache2

If it is already enabled, chances are you havent restarted apache2 or
launched the koha-plack process.

Good luck!

-- 
Tomás Cohen Arazi
Theke Solutions (https://theke.io )
✆ +54 9351 3513384
GPG: B2F3C15F
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Koha Performance

[JanM]

Activated Memcached and now I gained about 2 Seconds. So a request takes
about 6 Seconds.
I also made a request to add another CPU Core to the system. Hope this
helps. 

I took a look at another Koha Setup:
http://catalogue.demo1711-koha.test.biblibre.eu/cgi-bin/koha/opac-search.pl?idx==Forschung

This is my Setup:
https://www.testothek.uni-hamburg.de

The Performance difference is huge, hope I'll get there...

I'll keep you updated, thanks for now!
Jan



--
Sent from: http://koha.1045719.n5.nabble.com/Koha-general-f3047918.html
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Koha Performance

[Tomas Cohen Arazi]

I would raise the cores count (two cores) and make sure memcached is
installed and configured.

To install memcached (on te Koha server):

$ sudo apt install memcached

To configure memcached to be used by Koha, make sure the relevant
koha-conf.xml file contains something that looks like this:

 127.0.0.1:11211
 koha_koha

Tell us how it goes!

El lun., 19 mar. 2018 a las 11:35, JanM ()
escribió:

> /Koha-Version:  17.11.03.000
> OS Version ('uname -a'):Linux www2 4.4.0-96-generic #119-Ubuntu
> SMP Tue
> Sep 12 14:59:54 UTC 2017 x86_64
> Perl Interpreter:   /usr/bin/perl
> Perl-Version:   5.022001
> Perl @INC:  /usr/share/koha/lib
> /etc/perl
> /usr/local/lib/x86_64-linux-gnu/perl/5.22.1
> /usr/local/share/perl/5.22.1
> /usr/lib/x86_64-linux-gnu/perl5/5.22
> /usr/share/perl5
> /usr/lib/x86_64-linux-gnu/perl/5.22
> /usr/share/perl/5.22
> /usr/local/lib/site_perl
> /usr/lib/x86_64-linux-gnu/perl-base
> .
> MySQL-Version:  mysql Ver 15.1 Distrib 10.0.34-MariaDB, for
> debian-linux-gnu
> (x86_64) using readline 5.2
> Apache-Version: Server version: Apache/2.4.18 (Ubuntu)
> Memcached:  Server: Nicht definiert | Namespace: koha | Status:
> unbekannt |
> Konfiguration gelesen aus: Nirgendwo Bitte beachten Sie, dass die
> Memcached-Konfiguration in Iher $KOHA_CONF-Datei erfolgen sollte. Aktuell
> gibt es keine gültige Memcached-Konfiguration. | Aktive Caching-Methode:
> Cache::Memory/
>
>
>
> Running on an Intel Xeon X6550. Virtual Machine (VMWare) with 1 Core. 16Gb
> Ram.
> Memcache is not enabled. I have no information about the DB Server, it is
> provided from our computer center. We trace the request from the webserver
> an had about 2ms process time per request. So at 4000 querys we talk about
> 8
> Seconds. That would explain much of the 10 Seconds delay (4000Querys * 2ms
> =
> 8 Seconds.)
>
>
>
> --
> Sent from: http://koha.1045719.n5.nabble.com/Koha-general-f3047918.html
> ___
> Koha mailing list  http://koha-community.org
> Koha@lists.katipo.co.nz
> https://lists.katipo.co.nz/mailman/listinfo/koha
>
-- 
Tomás Cohen Arazi
Theke Solutions (https://theke.io )
✆ +54 9351 3513384
GPG: B2F3C15F
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Koha Performance

[JanM]

/Koha-Version:  17.11.03.000
OS Version ('uname -a'):Linux www2 4.4.0-96-generic #119-Ubuntu SMP Tue
Sep 12 14:59:54 UTC 2017 x86_64
Perl Interpreter:   /usr/bin/perl
Perl-Version:   5.022001
Perl @INC:  /usr/share/koha/lib
/etc/perl
/usr/local/lib/x86_64-linux-gnu/perl/5.22.1
/usr/local/share/perl/5.22.1
/usr/lib/x86_64-linux-gnu/perl5/5.22
/usr/share/perl5
/usr/lib/x86_64-linux-gnu/perl/5.22
/usr/share/perl/5.22
/usr/local/lib/site_perl
/usr/lib/x86_64-linux-gnu/perl-base
.
MySQL-Version:  mysql Ver 15.1 Distrib 10.0.34-MariaDB, for debian-linux-gnu
(x86_64) using readline 5.2
Apache-Version: Server version: Apache/2.4.18 (Ubuntu)
Memcached:  Server: Nicht definiert | Namespace: koha | Status: unbekannt |
Konfiguration gelesen aus: Nirgendwo Bitte beachten Sie, dass die
Memcached-Konfiguration in Iher $KOHA_CONF-Datei erfolgen sollte. Aktuell
gibt es keine gültige Memcached-Konfiguration. | Aktive Caching-Methode:
Cache::Memory/



Running on an Intel Xeon X6550. Virtual Machine (VMWare) with 1 Core. 16Gb
Ram. 
Memcache is not enabled. I have no information about the DB Server, it is
provided from our computer center. We trace the request from the webserver
an had about 2ms process time per request. So at 4000 querys we talk about 8
Seconds. That would explain much of the 10 Seconds delay (4000Querys * 2ms =
8 Seconds.) 



--
Sent from: http://koha.1045719.n5.nabble.com/Koha-general-f3047918.html
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Koha Performance

[Tomas Cohen Arazi]

Hi Jan, could you tell us more about your setup?

- Koha version?
- Is memcached enabled and functional? More > About > System information
- Any other problems reported in About page?
- Specs for the server
- External DB server?

Regards

El lun., 19 mar. 2018 a las 7:12, JanM ()
escribió:

> Hi,
>
> i'm new to Koha and at the university i'm working at we have a small
> library
> with about 50 items.
> We have a small server where Koha is running on. Plack is also enabled. We
> are running a Mariadb on an other server.
>
> The problem is, that it takes about 10 seconds for a request to be
> answered.
> In example a User is searching for "Alters-Konzentrations-Test" and the
> result takes about 10 seconds. Also the whole navigation on the page feels
> slow.
>
> Per search request there are about 4000 queries sent to the database
> server,
> is this normal? What else can I check?
>
> Kind regards
> Jan
>
>
>
> --
> Sent from: http://koha.1045719.n5.nabble.com/Koha-general-f3047918.html
> ___
> Koha mailing list  http://koha-community.org
> Koha@lists.katipo.co.nz
> https://lists.katipo.co.nz/mailman/listinfo/koha
>
-- 
Tomás Cohen Arazi
Theke Solutions (https://theke.io )
✆ +54 9351 3513384
GPG: B2F3C15F
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Koha Performance Issue

[rfblanchard]

Yea i used sudo apt-get install koha-common

Thanks for that advice. I seen mentions of plack here and there but didn't
know much about it.
I enabled plack:
> sudo koha-plack --enable  
> sudo koha-plack --start 
and memcached:
> USE_MEMCACHED="yes"
> SetEnv MEMCACHED_SERVERS "127.0.0.1:11211"
> SetEnv MEMCACHED_NAMESPACE "koha_peischool"

That did make a performance difference in the speed of koha.



--
View this message in context: 
http://koha.1045719.n5.nabble.com/Koha-Performance-Issue-tp5905752p5905918.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

Re: [Koha] Koha Performance Issue

[Jonathan Druart]

Hi Martin,

You can have a look at the server load to know if it's busy.
You will need to fix your network issues before inspecting any else I'd say.

Regards,
Jonathan

2016-10-03 21:02 GMT+02:00 Martin House :
> Out of curiosity, does the amount of RAM make a significant difference?
> I've been trying to troubleshoot performance issues because of both network
> lag at our location. In trying to optimize the page-load speed during
> checkout, I've also upped the serve RAM to from 1gig to 4gigs. While that
> obviously doesn't address actual network lag (eg. bad pings or lost
> packets) it can at least help me verify if the issue is with my Koha server
> or with the building network. We are in a leased building, and have no
> control over the network infrastructure, so if I can rule out the server as
> a speed hindrance, then I can restart the conversation with IT.
>
> Thanks,
>
> Martin
>
> Martin House
> martin.ho...@gmail.com
> www.martindhouse.com
> 704-996-0297
> "An unexamined life is not worth living."
>
>
> On Mon, Oct 3, 2016 at 2:50 PM, Chris Cormack 
> wrote:
>
>> * rfblanchard (rfblanch...@hotmail.com) wrote:
>> > I'm building a new koha server to replace our old koha 3.0.0 with koha
>> > 16.5.4. The new server has better specs than the old one. Towards the
>> end of
>> > my work I started doing some basic testing of the screens compared to the
>> > old system. I noticed the new system is slower (much slower) than our old
>> > 3.0 koha. Basically any screen is 5x to 10x slower on the new version of
>> > koha. That includes anything from searching to loading the landing page
>> of
>> > the opac. I checked on some of the koha demo sites and also noticed they
>> are
>> > quite slow. Has koha just become bloated over time or have I
>> misconfigured
>> > something?
>> >
>> > I didn't build the original server, but I compared apache and mysql
>> settings
>> > and didn't notice anything that the new install was missing. I tried
>> using
>> > memcached but that did nothing useful as far as I noticed.
>> >
>> > Does anyone have any insite into speeding up koha performance? caching?
>> etc?
>> >
>> Koha now uses a database independent layer an ORM (Object relationship
>> model).
>> This allows (in theory) Koha to be run on different database engines, it
>> also allows
>> for more Object Oriented code, which a lot of people like.
>>
>> It does have the downside of being quite a bit slower than straight SQL
>> though, this
>> accounts for most of the slow down you are noticing.
>>
>> Did you install Koha via packages? If so, you will want to switch plack on
>>
>> sudo koha-plack --enable 
>> sudo koha-plack --start 
>>
>> Then restart apache. You will want to set up memcache as well. To enable
>> caching
>> to occur. This should speed things up considerably.
>>
>> Chris
>> --
>> Chris Cormack
>> Catalyst IT Ltd.
>> +64 4 803 2238
>> PO Box 11-053, Manners St, Wellington 6142, New Zealand
>>
>> ___
>> Koha mailing list  http://koha-community.org
>> Koha@lists.katipo.co.nz
>> https://lists.katipo.co.nz/mailman/listinfo/koha
>>
>>
> ___
> Koha mailing list  http://koha-community.org
> Koha@lists.katipo.co.nz
> https://lists.katipo.co.nz/mailman/listinfo/koha
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Koha Performance Issue

[Jonathan Druart]

Hi,

What are  the specs of your server?
Koha 3.0 and Koha 16.05 are completely different in term of features
and architecture.
I would recommend you to start a fresh install using packages
(https://wiki.koha-community.org/wiki/Koha_on_Debian), re-inject your
DB and upgrade it.
Then you must enable plack and memcached to really enjoy Koha :)

Don't hesitate to jump into our #koha irc channel!

Regards,
Jonathan

2016-10-03 20:42 GMT+02:00 rfblanchard :
> I'm building a new koha server to replace our old koha 3.0.0 with koha
> 16.5.4. The new server has better specs than the old one. Towards the end of
> my work I started doing some basic testing of the screens compared to the
> old system. I noticed the new system is slower (much slower) than our old
> 3.0 koha. Basically any screen is 5x to 10x slower on the new version of
> koha. That includes anything from searching to loading the landing page of
> the opac. I checked on some of the koha demo sites and also noticed they are
> quite slow. Has koha just become bloated over time or have I misconfigured
> something?
>
> I didn't build the original server, but I compared apache and mysql settings
> and didn't notice anything that the new install was missing. I tried using
> memcached but that did nothing useful as far as I noticed.
>
> Does anyone have any insite into speeding up koha performance? caching? etc?
>
>
>
>
>
> --
> View this message in context: 
> http://koha.1045719.n5.nabble.com/Koha-Performance-Issue-tp5905752.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
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Koha Performance Issue

[Martin House]

Out of curiosity, does the amount of RAM make a significant difference?
I've been trying to troubleshoot performance issues because of both network
lag at our location. In trying to optimize the page-load speed during
checkout, I've also upped the serve RAM to from 1gig to 4gigs. While that
obviously doesn't address actual network lag (eg. bad pings or lost
packets) it can at least help me verify if the issue is with my Koha server
or with the building network. We are in a leased building, and have no
control over the network infrastructure, so if I can rule out the server as
a speed hindrance, then I can restart the conversation with IT.

Thanks,

Martin

Martin House
martin.ho...@gmail.com
www.martindhouse.com
704-996-0297
"An unexamined life is not worth living."


On Mon, Oct 3, 2016 at 2:50 PM, Chris Cormack 
wrote:

> * rfblanchard (rfblanch...@hotmail.com) wrote:
> > I'm building a new koha server to replace our old koha 3.0.0 with koha
> > 16.5.4. The new server has better specs than the old one. Towards the
> end of
> > my work I started doing some basic testing of the screens compared to the
> > old system. I noticed the new system is slower (much slower) than our old
> > 3.0 koha. Basically any screen is 5x to 10x slower on the new version of
> > koha. That includes anything from searching to loading the landing page
> of
> > the opac. I checked on some of the koha demo sites and also noticed they
> are
> > quite slow. Has koha just become bloated over time or have I
> misconfigured
> > something?
> >
> > I didn't build the original server, but I compared apache and mysql
> settings
> > and didn't notice anything that the new install was missing. I tried
> using
> > memcached but that did nothing useful as far as I noticed.
> >
> > Does anyone have any insite into speeding up koha performance? caching?
> etc?
> >
> Koha now uses a database independent layer an ORM (Object relationship
> model).
> This allows (in theory) Koha to be run on different database engines, it
> also allows
> for more Object Oriented code, which a lot of people like.
>
> It does have the downside of being quite a bit slower than straight SQL
> though, this
> accounts for most of the slow down you are noticing.
>
> Did you install Koha via packages? If so, you will want to switch plack on
>
> sudo koha-plack --enable 
> sudo koha-plack --start 
>
> Then restart apache. You will want to set up memcache as well. To enable
> caching
> to occur. This should speed things up considerably.
>
> Chris
> --
> Chris Cormack
> Catalyst IT Ltd.
> +64 4 803 2238
> PO Box 11-053, Manners St, Wellington 6142, New Zealand
>
> ___
> Koha mailing list  http://koha-community.org
> Koha@lists.katipo.co.nz
> https://lists.katipo.co.nz/mailman/listinfo/koha
>
>
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Koha Performance Issue

[Chris Cormack]

* rfblanchard (rfblanch...@hotmail.com) wrote:
> I'm building a new koha server to replace our old koha 3.0.0 with koha
> 16.5.4. The new server has better specs than the old one. Towards the end of
> my work I started doing some basic testing of the screens compared to the
> old system. I noticed the new system is slower (much slower) than our old
> 3.0 koha. Basically any screen is 5x to 10x slower on the new version of
> koha. That includes anything from searching to loading the landing page of
> the opac. I checked on some of the koha demo sites and also noticed they are
> quite slow. Has koha just become bloated over time or have I misconfigured
> something?
> 
> I didn't build the original server, but I compared apache and mysql settings
> and didn't notice anything that the new install was missing. I tried using
> memcached but that did nothing useful as far as I noticed.
> 
> Does anyone have any insite into speeding up koha performance? caching? etc?
> 
Koha now uses a database independent layer an ORM (Object relationship model).
This allows (in theory) Koha to be run on different database engines, it also 
allows
for more Object Oriented code, which a lot of people like.

It does have the downside of being quite a bit slower than straight SQL though, 
this
accounts for most of the slow down you are noticing.

Did you install Koha via packages? If so, you will want to switch plack on

sudo koha-plack --enable 
sudo koha-plack --start 

Then restart apache. You will want to set up memcache as well. To enable caching
to occur. This should speed things up considerably.

Chris
-- 
Chris Cormack
Catalyst IT Ltd.
+64 4 803 2238
PO Box 11-053, Manners St, Wellington 6142, New Zealand


signature.asc
Description: PGP signature
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha