|
in reply to Perl with a Samba mount
IMHO you'll always come across performance bumps when using network drives. How can you tell for sure that non-perl programs don't have that problem? Are they accessing those 60,000 files as well? For Perl, a file is a file, no creed or col.. uhm no extension or filesystem makes really a difference. That's all stuff the underlying OS will have to do.
Ofcourse, chances are someone with p5p will now smack me right in the face and deny every little detail of my node :) but that's how it makes most sense to me.
Greetz
Beatnik
... Quidquid perl dictum sit, altum viditur. |
Re: Re: Perl with a Samba mount
by fletcher_the_dog (Friar) on Jan 03, 2003 at 15:18 UTC
|
"IMHO you'll always come across performance bumps when using network drives. How can you tell for sure that non-perl programs don't have that problem? Are they accessing those 60,000 files as well? "
Yes, in fact they run over the exact same 60,000 files. There is a slight performance bump of ~30 seconds, from 13m14s to 13m35s. Compare this to a 2+ hour increase. | [reply] |
|
|
I assume those non-perl programs are binaries? In some recent testing I did in image manipulation, a pure C solution linked to libgd was about 50 times faster than a perl solution linked to GD.pm. Perl scripts, by nature, are slower than binary applications. Perl scripts need to be interpreted. There are entire layers of logic between how you program it and how the system eventually executes the code eventually generated by the underlying endgine. It all depends on how your code is written :) Maybe it's time to grab Devel::DProf and have a field day tweaking :)
Greetz
Beatnik
... Quidquid perl dictum sit, altum viditur.
| [reply] |
|
