RE: hotlinking and server opinion

I think EIDE is a bad idea for squid, especially with just ONE drive.

You'll be logging to this drive, and you'll be caching to this drive, plus all
the other stuff your host OS does to the drive. My 750+ users quickly overran
a single FW-SCSI-2 drive in a 2 CPU Origin 200. Adding a second drive for
just the cache swap helped relieve this bottleneck, but the cache drive still
peaks at around 80% utilization, which is just too high for comfort. I plan
to stripe the cache drive into a multi-spindle volume. But you can't easily
do this with EIDE, since the IDE bus is not shared - when one drive is busy
the other one waits. You can add a second drive as a master on the secondary
IDE port, but that's as far as you can expand.

Go with SCSI, use multiple drives. Otherwise, your squid cache will be
spending most of it's time waiting on I/O. Load will be high but CPU
utilization will be very low. You'll waste the PII-350 if you use EIDE.

> -----Original Message-----
> From: Justin Smith [mailto:blacula@execpc.com]
> Sent: Wednesday, May 12, 1999 11:46 AM
> To: squid-users@ircache.net
> Subject: hotlinking and server opinion
>
>
> I am looking at building a squid box as a http accelerator for an existing
> apache box that is getting over 250k+ hits a day. Due to the cgi work on
> that server, it is getting a little busy.
>
> My plan is to use the squid box as the front end handling all static
> graphics and images. While the existing box handles the rest using the
> squid box as its gateway.
>
> Here is my problem. I do not know if hotlinking would be stopped. I am
> running a freehost and I do not want users to have their site located on
> another site and link to my site for only images. Currently, the machines
> .htaccess takes care of that and I am curious if the reverse proxy will
> recognize this.
>
> Second, I plan on buidling a PII 350/384megs/10gig EIDE drive. Anyone
> with any good/bad stories to report
>
> Thanks
> Justin
>
Received on Thu May 13 1999 - 12:07:18 MDT