XFS Pro mod_perl request poll

mrperl · Joined: 06 Mar 2010 Posts: 65

Hi folks.

Please answer this poll about requesting mod_perl support for XFS Pro.

mod_perl can run Perl programs several times faster than regular cgi-bin.

It would take Alex about 2 days for the code changes to support mod_perl well.

Thanks, mrperl.

ankurs · Joined: 10 Mar 2009 Posts: 515

i would like it rewritten, if it can run perl/cgi on ngnix

then i can get rid of apache from all my servers

komi · Joined: 27 Nov 2009 Posts: 159

That would be great!

komi · Joined: 27 Nov 2009 Posts: 159

Is this going to happen?

Speed is one of the most important factors of a website. It would be nice if XFS is compatible with mod_perl.

PilgrimX182 · Joined: 22 Mar 2006 Posts: 2109 Location: UFO Lab

ankurs, apache is still required for mod_perl.

komi, we're working on advanced mod_perl version of XFS nowdays, so it's 100% gonna happen. Can't tell any dates though.

komi · Joined: 27 Nov 2009 Posts: 159

Wondering what the status is. Is it really that much work?

mrperl · Joined: 06 Mar 2010 Posts: 65

It would take about 2 days to cleanup the 1.7 source for ModPerl::Registry, as long as the encryption module isn't the source of segfaults. 3x faster than plain CGI. (The source would still work under plain CGI on any webserver.)

It would take about a month to convert to mod_perl handlers and test it. 10x faster than plain CGI, or more. (Source would only work under Apache/mod_perl.)

mrperl

chrda · Joined: 14 Sep 2009 Posts: 227

Sounds like its needed for sure Smile

Still in the long run i think nginx is needed as backend for files.

komi · Joined: 27 Nov 2009 Posts: 159

stunna · Joined: 25 Apr 2010 Posts: 44

script is a perl script, the apache is just the caller, the perl is the killer, it's because of calling perl as a program every time somebody accesses a page. the script is quite heavy and requires some modules to load .so the mod_perl in apache would save the day , however, there is even better possibility
with lighttpd and perl fastcgi process. because mod_perl is fast, but the original perl binary is (usually) faster. and if it is used as a fastcgi (not cgi), then it will always stay in memory and won't have to always load and unload all the data.

I am coding upload.cgi for mod_perl now and will test it against lighty , fast cgi .And nginx or lighty for downloads.

nik0la · Joined: 30 Dec 2009 Posts: 102

How is going with mod_perl version? when will be released?

ankurs · Joined: 10 Mar 2009 Posts: 515

i am guess with 1.8 , they will release with mod_perl version

mastypk · Joined: 04 Apr 2010 Posts: 124

Any news about new version???

mrperl · Joined: 06 Mar 2010 Posts: 65

The author modified the XFS Pro 1.8 files in FS-dist, so it is ModPerl-compatible.

It is working for me on a fileserver (fs) with this config:

mrperl · Joined: 06 Mar 2010 Posts: 65

I have been doing more testing using Modperl::PerlRun on the fileserver.

If you use multiple fs configurations on the same machine in different directories, then PerlRun confuses $c in XFSConfig.pm, so api.cgi fails on fs_key (ie. wrong configuration parameters are loaded even if in different subdirectories.)