Heya Jonathan, To get much of the benefit of mod_perl, without requiring a re-write of the CGIs, you can use mod_perl along with Apache::Registry module. You'll notice quite a speed up with this, as the scripts will be pre-compiled (and only reloaded if they have changed since the last time they were called).
Take care, Mark. On Sat, 13 Apr 2002, Jonathan wrote: > > The opensrs scripts seems to be relatively large and is > only seems to be getting bigger with time. > > Does anyone or the developers know whether the > current 80KB script size has a significant > enough impact on how fast the scripts > can be run and compiled as opposed to a 40KB script? > > I'm wondering if breaking up the current register.cgi and manage.cgi > scripts into smaller individual components will have much of > an effect on speed to make it worthwhile. > > Currently, upon looking at the CPU % used evertime the manage.cgi script > is invoked, it seems to use up 17% to 28% of my CPU resouces > during the compile process. > The cpu % numbers were come from data run on a Dual P3 1GHZ with 512K cache > with a cheetah SCSI. > > Does anyone know how to improve speed and performance of those scripts. > > I hear converting over to PHP speeds things up, but that'll take > a lot of work, and sometimes I hear of PHP security flaws. > mod_perl is an alternative, but can be very dangerous if > you're not very careful with your code. > > Since perl is a compiled everytime language, I'm wondering if > I can shorten the compile time by switching the machine > to much faster processor. The idea behind this is that > a faster processor and BUS will speed up the perl compile time > and make it a minimal factor. > > With this in mind, do you think there will be a significant > performance difference if I switch over to a: > > Dual 2.0 GHZ Xeon with 2GB of Rambus memory and a 15,000K RPM > cheetah harddrive? I know the BUS on the Xeons run > about close to 4 times faster than the standard > P3's. Wonder if speeding up the compile time would > make enough difference to make this switch worthwhile. > > Jonathan Lee > Tech Manager > 415-682-3859 > http://123cheapdomains.com > > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On > Behalf Of [EMAIL PROTECTED] > Sent: Saturday, April 13, 2002 7:45 PM > To: John W. Roche IV > Cc: OpenSRS Dev-List (E-mail) > Subject: Re: OpenSRS Whois > > > > On Sat, 13 Apr 2002, John W. Roche IV wrote: > > > Umm, why is the whois output for microsoft.com, kind of , well, unusual? > > You are viewing a list of name server hosts registered at the registry. > > Just people taking advantage of the way the registry whois does a wildcard > search of all domains, name server hosts and contacts. > > > And how is this accomplished? > > Register a name server host with "microsoft.com" as the first part of its > name, for example "microsoft.com.einfosystems.net" > > >
