Perl and my PC Processor

Marty_

I'm running 2gig memory, however my windows task manger never goes above 13.700k of memory when running perl.exe having said that my perl site does crash when 2-3 users are on line, I get the 500 internal server error.
My question is, if I change my PC from a mere 1.3ghz to a 3.2ghz processor will this help ?

Marty_

just for the hell of it i switched the hard drive into a 3ghz machine, load times in half straight away, but my site still crashes when trying to load tables(into mysql) from a perl script.
Basically perl is load of cr***... or what ?

AbyssUnderground

Marty_ wrote
just for the hell of it i switched the hard drive into a 3ghz machine, load times in half straight away, but my site still crashes when trying to load tables(into mysql) from a perl script.
Basically perl is load of cr***... or what ?

Perl isn't usually a first choice for handling databases in MySQL, PHP however is. I don't see why you should get a 500 error. Have you tried an older version of perl to see if this helps?

aprelium

Marty_ wrote
I'm running 2gig memory, however my windows task manger never goes above 13.700k of memory when running perl.exe having said that my perl site does crash when 2-3 users are on line, I get the 500 internal server error.
My question is, if I change my PC from a mere 1.3ghz to a 3.2ghz processor will this help ?

Check the cgi.log to know why Perl has stopped working. This may help you debug the scripts and understand what is going wrong.
Your problem looks a lot like a badly coded script. Perl is not to be blamed because of a bad script. It cannot do miracles when you ask it to run a buggy piece of code.

aprelium

Marty_,
Check your cgi.log file to get the detailed error messages Perl output when the script failed.
What you describe looks more like a script bug than a Perl problem.

Marty_

aprelium wrote
Marty_,
Check your cgi.log file to get the detailed error messages Perl output when the script failed.
What you describe looks more like a script bug than a Perl problem.

Noting there only the broken pipe message, anyway I made some changes in mysql my.ini file and that has helped a lot, but alas some times the site will crash with extra load while I'm running an admin scripts. Its also not just that script that will cause a load.
Is there no way to increase the amount of memory perl.exe uses ?

admin

Marty_ wrote
Is there no way to increase the amount of memory perl.exe uses ?

Perl will use the memory as it needs it. There is no correlation between the fact that your script does not work and the fact that your script does not work as expected.
Perl did not crash (it's not like a blue screen of death of Windows), it has simply stopped before sending any information to the Web server. According to our experience, this is always a sign of a script that is failing at its early stages. So we strongly suggest that you review the script or ask its author for help.
Chances that your script is bad or has a bug are way higher than the chance that Perl is misbehaving.

twotone

AbyssUnderground wrote
Perl isn't usually a first choice for handling databases in MySQL, PHP however is.

That is quite a statement to make about perl and php. Are you sure you are correct? I think both have their uses. See the following for some comparisons expounding the strengths of both:
http://www.oreillynet.com/onlamp/blog/2004/08/perl_versus_php_5.html
http://www.mediacollege.com/internet/perl/perl-vs-php.html
http://www.serverwatch.com/tutorials/article.php/10825_1126681_1
http://tnx.nl/php
http://use.perl.org/articles/00/04/17/190245.shtml
I probably can't give you any help to fix your problem, but I can tell you that you should be able to. I run Perl all the time with abyss on my laptop with mysql. I designed a completely dynamic site with content management and file upload using perl -- all the info is stored in a mysql database and retrieved when the page is constructed. (see the site at www.theduttons.com). I write and test the code on my laptop using abyss and then update the live site (running on apache). I've never had any problems with abyss or perl or mysql running slowly on my laptop, but I usually only have 1 connection active at a time to my abyss server.
Have you looked at the abyss server settings to see if it is limiting the number of connections or the bandwith when a certain number of connections are active? You probably have.
If you want, I could look at your perl code to see if I notice anything that could cause the problem. I can't promise anything, though. I will send you a message with my email address.

Marty_

twotone wrote

AbyssUnderground wrote
Perl isn't usually a first choice for handling databases in MySQL, PHP however is.

That is quite a statement to make about perl and php. Are you sure you are correct? I think both have their uses. See the following for some comparisons expounding the strengths of both:
http://www.oreillynet.com/onlamp/blog/2004/08/perl_versus_php_5.html
http://www.mediacollege.com/internet/perl/perl-vs-php.html
http://www.serverwatch.com/tutorials/article.php/10825_1126681_1
http://tnx.nl/php
http://use.perl.org/articles/00/04/17/190245.shtml
I probably can't give you any help to fix your problem, but I can tell you that you should be able to. I run Perl all the time with abyss on my laptop with mysql. I designed a completely dynamic site with content management and file upload using perl -- all the info is stored in a mysql database and retrieved when the page is constructed. (see the site at www.theduttons.com). I write and test the code on my laptop using abyss and then update the live site (running on apache). I've never had any problems with abyss or perl or mysql running slowly on my laptop, but I usually only have 1 connection active at a time to my abyss server.
Have you looked at the abyss server settings to see if it is limiting the number of connections or the bandwith when a certain number of connections are active? You probably have.
If you want, I could look at your perl code to see if I notice anything that could cause the problem. I can't promise anything, though. I will send you a message with my email address.

Thanks for the reply and your offer in a PM received, however the problem wasn't down to perl and everything is running 100%.
After adjusting mysql settings via my.ini from default-storage-engine=INNODB-MyISAM
...and reloading all tables, my site runs like a dream or rather the way it should.
Basically as a result of my original tables getting larger and larger the INNODB settings where of no use and they couldn't handle the sql commands, thus internal server error was happing regularly.

twotone

Cool.
Just found a really cool article/study about craig's list that is loosely related to this thread. They use mysql databases that range from 11GB to 40GB in size with row counts from 1,000,000 to 100,000,000. All of the database content is accessed and served up as web pages by perl.