Hello all, has anyone set up mod perl on a koha instance? And if so, are there any bugs or issues doing this? It seems we tried it some time ago, and this page says there are issues, but doesn't give more details: http://wiki.koha-community.org/wiki/Koha_Tuning We have been testing it today and i haven't seen serious issues so far. From the wiki it seems the latest tests were made 4 years ago, so it's possible things have changed in Koha and mod_perl. It's something worth trying at any rate, because the mod perl documentation claims "400% to 2000%" performance boosts. It definitely feels *much* faster on our test instance right now. -- Gaetan Boisson Chef de projet bibliothécaire BibLibre 06 52 42 51 29 108 avenue Breteuil 13006 Marseille gaetan.boisson@biblibre.com
Le 27/05/2015 11:22, Gaetan Boisson a écrit :
Hello all, Hello, has anyone set up mod perl on a koha instance? And if so, are there any bugs or issues doing this? Theory : Plack & mod_perl are using the same kind of idea to embed Perl (for Plack it's in specific plackup/starman process, for mod_perl it's in Apache itself).
The reason why mod_perl was not working well are probably the same reason why Plack was not working well (ie: nested sub & variable scope problem). They have been fixed for supporting Plack, it's not a surprise to me that they fixed the mod_perl problems. It also mean that the performance improvement should also be comparable. Question 1: what could make us face problem with Plack that does not appear on mod_perl ? Question 2: why should we prefer Plack vs mod_perl ? (in the short term and/or in the long term) Question 3: any side effect that we haven't found yet ?
It seems we tried it some time ago, and this page says there are issues, but doesn't give more details: http://wiki.koha-community.org/wiki/Koha_Tuning
We have been testing it today and i haven't seen serious issues so far. From the wiki it seems the latest tests were made 4 years ago, so it's possible things have changed in Koha and mod_perl.
It's something worth trying at any rate, because the mod perl documentation claims "400% to 2000%" performance boosts. It definitely feels *much* faster on our test instance right now.
-- Paul Poulain, Associé-gérant / co-owner BibLibre, Services en logiciels libres pour les bibliothèques BibLibre, Open Source software and services for libraries
I've been using mod_perl on a different project lately, and I think Paul is right about why mod_perl might not have worked well in the past and probably works better now. As far as I know, both mod_perl and Plack gain "persistence" through a combination of pre-loading Perl modules and caching compiled code. ( If you do run into problems, I imagine they might be subtle at this point? With the mod_perl project, I notice that we still have some variable scope issues where values sometimes get cached in unexpected ways. As for Paul's Question 2, I think most projects these days are favouring Plack/PSGI. I think mod_perl might be a bit old-fashioned these days, although it certainly seems to work well still. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St, Ultimo, NSW 2007
-----Original Message----- From: koha-devel-bounces@lists.koha-community.org [mailto:koha-devel- bounces@lists.koha-community.org] On Behalf Of Paul Poulain Sent: Wednesday, 27 May 2015 7:33 PM To: koha-devel@lists.koha-community.org Subject: Re: [Koha-devel] Koha and mod perl
Le 27/05/2015 11:22, Gaetan Boisson a écrit :
Hello all, Hello, has anyone set up mod perl on a koha instance? And if so, are there any bugs or issues doing this? Theory : Plack & mod_perl are using the same kind of idea to embed Perl (for Plack it's in specific plackup/starman process, for mod_perl it's in Apache itself).
The reason why mod_perl was not working well are probably the same reason why Plack was not working well (ie: nested sub & variable scope problem). They have been fixed for supporting Plack, it's not a surprise to me that they fixed the mod_perl problems.
It also mean that the performance improvement should also be comparable.
Question 1: what could make us face problem with Plack that does not appear on mod_perl ? Question 2: why should we prefer Plack vs mod_perl ? (in the short term and/or in the long term) Question 3: any side effect that we haven't found yet ?
It seems we tried it some time ago, and this page says there are issues, but doesn't give more details: http://wiki.koha-community.org/wiki/Koha_Tuning
We have been testing it today and i haven't seen serious issues so far. From the wiki it seems the latest tests were made 4 years ago, so it's possible things have changed in Koha and mod_perl.
It's something worth trying at any rate, because the mod perl documentation claims "400% to 2000%" performance boosts. It definitely feels *much* faster on our test instance right now.
-- Paul Poulain, Associé-gérant / co-owner BibLibre, Services en logiciels libres pour les bibliothèques BibLibre, Open Source software and services for libraries
_______________________________________________ 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/
David Cook schreef op ma 01-06-2015 om 10:30 [+1000]:
As for Paul's Question 2, I think most projects these days are favouring Plack/PSGI. I think mod_perl might be a bit old-fashioned these days, although it certainly seems to work well still.
I was curious, I'd heard that mod_perl was being deprecated slowly. Apparently that's not really the case, but there are other reasons. I asked on the wellington.pm IRC channel: <eythian> hey, what's the status of mod_perl these days? <eythian> is it being slowly deprecated? <morfran> i think it's just sliding quietly into obscurity <morfran> more portability; less reliance on apache; better tools; still being actively developed; less risk from abandonment of project <morfran> we're considering starman behind nginx as a replacement path for mod_perl <grantm> eythian: the main reason for plack over mod_perl is that plack can do everything with a much simpler API and it isn't tied to Apache <morfran> seems that mod_perl2 is actively developed <grantm> the mod_perl project has always been big, over complicated and under-resourced - but not dead -- Robin Sheat Catalyst IT Ltd. ✆ +64 4 803 2204 GPG: 5FA7 4B49 1E4D CAA4 4C38 8505 77F5 B724 F871 3BDF
Robin Sheat schreef op di 02-06-2015 om 12:06 [+1200]:
<morfran> more portability; less reliance on apache; better tools; still being actively developed; less risk from abandonment of project
I missed a paste where I asked about it in comparison to Plack, which makes this bit make more sense... -- Robin Sheat Catalyst IT Ltd. ✆ +64 4 803 2204 GPG: 5FA7 4B49 1E4D CAA4 4C38 8505 77F5 B724 F871 3BDF
Good info gathering, Robin! Yeah, I thought that mod_perl might be dead, but it looks like someone updated the home page of their website a little over a year ago, so someone still seems to be around. Having gone through both the mod_perl and Plack documentation, it does seem like using Plack is quite a bit more straightforward, more popular, Miyagawa seems active, and it takes away the Apache dependency (I wonder if that would make it harder or easier in terms of offering installation instructions and free support). A while back, I noticed that someone said the Catalyst framework wants to drop support for mod_perl but hasn't yet? So if Koha does eventually adopt a framework, it might make sense to go with Plack, which seems to be a focus for framework developers, while mod_perl is probably just added for compatibility at best. Just a few more of my two cents. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St, Ultimo, NSW 2007
-----Original Message----- From: koha-devel-bounces@lists.koha-community.org [mailto:koha-devel- bounces@lists.koha-community.org] On Behalf Of Robin Sheat Sent: Tuesday, 2 June 2015 10:06 AM To: koha-devel@lists.koha-community.org Subject: Re: [Koha-devel] Koha and mod perl
David Cook schreef op ma 01-06-2015 om 10:30 [+1000]:
As for Paul's Question 2, I think most projects these days are favouring Plack/PSGI. I think mod_perl might be a bit old-fashioned these days, although it certainly seems to work well still.
I was curious, I'd heard that mod_perl was being deprecated slowly. Apparently that's not really the case, but there are other reasons. I asked on the wellington.pm IRC channel:
<eythian> hey, what's the status of mod_perl these days? <eythian> is it being slowly deprecated? <morfran> i think it's just sliding quietly into obscurity <morfran> more portability; less reliance on apache; better tools; still being actively developed; less risk from abandonment of project <morfran> we're considering starman behind nginx as a replacement path for mod_perl <grantm> eythian: the main reason for plack over mod_perl is that plack can do everything with a much simpler API and it isn't tied to Apache <morfran> seems that mod_perl2 is actively developed <grantm> the mod_perl project has always been big, over complicated and under-resourced - but not dead
-- Robin Sheat Catalyst IT Ltd. ✆ +64 4 803 2204 GPG: 5FA7 4B49 1E4D CAA4 4C38 8505 77F5 B724 F871 3BDF
participants (4)
-
David Cook -
Gaetan Boisson -
Paul Poulain -
Robin Sheat