RE: Speed of current server

"Dennis Pinckard" <[email protected]>
Newsgroups gmane.network.up2date.current.devel
Message-ID <[email protected]>
 
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

OK, it's the laptop.  I suspected it would be.

I've configured another test box and it's currently getting close to
1000k/sec.  (W/o SSL)

That's cool.  The laptop was only to test current anyway.  It works.

Thanks folks.  Sorry for the false alarm!



- -----Original Message-----
From: Hunter Matthews [mailto:[email protected]]
Sent: Wednesday, March 20, 2002 4:15 PM
To: Current Server Mailing List
Subject: RE: [Current-server] Speed of current server


Check and see what your network speed is with ftp or nfs. Based on
the
performance here, I suspect you're not seeing a Current problem.


On Wed, 2002-03-20 at 16:24, Dennis Pinckard wrote:
>  
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Ok, I change the 'useNoSSLForPackages' to 1 and restarted the
> update process.  Now I'm getting 6k/second.  Hmmm.
> 
> All of these machines are in a test environment.  The file server
> is a single processor (1GHz PIII) w/512MB RAM and about 220GB of
> storage.  About the only thing on it right now is current and the
> redhat updates.  It also runs samba and openldap, but no one is
> using it.  The laptop is a IBM thinkpad 390x 500Mhz PIII w/512MB
> ram.  Just installed redhat 7.2 last night.  up2date is attempting
> to bring all of the packages up to date at once.
> 
> Could it be that the number of packages selected is causing a
> problem?
> 
> I forced an update of just up2date since the original version
> didn't include the 'useNoSSLForPackages' in the config file.  Only
> the
> Kernel and 100dpi &75dpi fonts are excluded.  (Anyone know why
> these fonts are also excluded?  My exclude list only has kernel*;
> listed.  Happens when updating from redhat as well.)
> 
> 
> 
> - -----Original Message-----
> From: Daniel P. Stasinski [mailto:[email protected]]
> Sent: Wednesday, March 20, 2002 3:02 PM
> To: [email protected]
> Subject: Re: [Current-server] Speed of current server
> 
> 
> > In general, right now performance is pretty bad.
> 
> Setting 'useNoSSLForPackages=1' in the up2date config speeded up
> the update process by an order of magnitude.
> 
> Daniel P. Stasinski
> Software Engineer
> Mayor Pharmaceutical Laboratories
> [email protected]
> 
> 
> 
> _______________________________________________
> Current-server mailing list
> [email protected]
> http://lists.dulug.duke.edu/mailman/listinfo/current-server
> 
> -----BEGIN PGP SIGNATURE-----
> Version: PGP 7.0.4
> 
> iQA/AwUBPJj+A3BWGat9hZ87EQJWYACfT+xKFFwclhOOklW1gJ9Hj01D2BkAoML+
> AfoiLOy/E86sehOY9huiEPJE
> =hOXh
> -----END PGP SIGNATURE-----
> 
> _______________________________________________
> Current-server mailing list
> [email protected]
> http://lists.dulug.duke.edu/mailman/listinfo/current-server
> 
> 
- -- 
Hunter Matthews                          Unix / Network Administrator
Office: BioScience 145/244               Duke Univ. Biology
Department
Key: F0F88438 / FFB5 34C0 B350 99A4 BB02  9779 A5DB 8B09 F0F8 8438
Never take candy from strangers. Especially on the internet.

_______________________________________________
Current-server mailing list
[email protected]
http://lists.dulug.duke.edu/mailman/listinfo/current-server

-----BEGIN PGP SIGNATURE-----
Version: PGP 7.0.4

iQA/AwUBPJkRbnBWGat9hZ87EQJKwQCeI2QZ6+smlWEeCI7GC8uZDCkvbDcAn21H
2/V3dqI9iDB6CDOOlCF1tmaL
=2AF/
-----END PGP SIGNATURE-----
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.