> Dan Anderson wrote:
>
> >
> > Very true. But you also need to look at what you're doing.
> A spider
> > that indexes or coallates pages across several sites might need to
> > slurp up a large number of pages -- which even at a few kilobytes a
> > piece would be costly on system resources.
Dan Anderson wrote:
Very true. But you also need to look at what you're doing. A spider
that indexes or coallates pages across several sites might need to slurp
up a large number of pages -- which even at a few kilobytes a piece
would be costly on system resources.
Ironically this is the one tim
On Thu, 2004-01-22 at 18:21, Dan Anderson wrote:
> On Thu, 2004-01-22 at 17:59, James Edward Gray II wrote:
> > On Jan 22, 2004, at 4:12 PM, Tim Johnson wrote:
> >
> > > Here's another argument against slurping: When you slurp a file all at
> > > once, even if your program isn't using up much of
On Thu, 2004-01-22 at 17:59, James Edward Gray II wrote:
> On Jan 22, 2004, at 4:12 PM, Tim Johnson wrote:
>
> > Here's another argument against slurping: When you slurp a file all at
> > once, even if your program isn't using up much of the CPU, on many
> > machines it will slow down performance
On Jan 22, 2004, at 4:12 PM, Tim Johnson wrote:
Here's another argument against slurping: When you slurp a file all at
once, even if your program isn't using up much of the CPU, on many
machines it will slow down performance considerably if you slurp a
large
file (large, of course, is still some
> Here's another argument against slurping: When you slurp a
> file all at once, even if your program isn't using up much of
> the CPU, on many machines it will slow down performance
> considerably if you slurp a large file (large, of course, is
> still sometimes relative). If that is the onl
> > Good comparison, I never see advice to use no warnigns and
> no strict
> > though :)
>
> I've actually seen it a few times in code, but it's usually surrounded
> by:
>
> ##
> ##
> #WARNING!!
> ##
> # Warnings / Strict
assume that.
-Original Message-
From: Dan Muey [mailto:[EMAIL PROTECTED]
Sent: Thursday, January 22, 2004 1:49 PM
To: Dan Anderson
Cc: Perl Beginners Mailing List
Subject: RE: Survey : Max size allowable for slurping files
Good comparison, I never see advice to use no warnigns and no
On Thu, 2004-01-22 at 16:49, Dan Muey wrote:
> > > But I see a lot of "don't slurp that" and I was hoping for more
> > > clear reasons/situatuions to or not to slurp so people
> > positn code can have a better idea why a perosn said:
> > > "do(n't) slurp your file here"
> > >
> > > Basically we n
> > But I see a lot of "don't slurp that" and I was hoping for more
> > clear reasons/situatuions to or not to slurp so people
> positn code can have a better idea why a perosn said:
> > "do(n't) slurp your file here"
> >
> > Basically we need to expalin why more:
> >
> > - Don't slurp this beca
On Thu, 2004-01-22 at 16:32, Dan Muey wrote:
> > On Thu, 2004-01-22 at 16:16, Dan Muey wrote:
> > > > On Thu, 2004-01-22 at 13:18, Dan Muey wrote:
> > > > > There are always comments like "you can slurp the file
> > as long as
> > > > > it's not too big" or "becareful not to slurp a really
> > b
> On Thu, 2004-01-22 at 16:16, Dan Muey wrote:
> > > On Thu, 2004-01-22 at 13:18, Dan Muey wrote:
> > > > There are always comments like "you can slurp the file
> as long as
> > > > it's not too big" or "becareful not to slurp a really
> big file or
> > > > you'll be in trouble".
> > >
> > > I
On Thu, 2004-01-22 at 16:16, Dan Muey wrote:
> > On Thu, 2004-01-22 at 13:18, Dan Muey wrote:
> > > There are always comments like "you can slurp the file as
> > > long as it's not too big" or "becareful not to slurp a
> > > really big file or you'll be in trouble".
> >
> > I'd like to add that s
> On Thu, 2004-01-22 at 13:18, Dan Muey wrote:
> > There are always comments like "you can slurp the file as
> > long as it's not too big" or "becareful not to slurp a
> > really big file or you'll be in trouble".
>
> I'd like to add that some of it depends on swap space. I've
> slurped well pa
On Thu, 2004-01-22 at 13:18, Dan Muey wrote:
> There are always comments like "you can slurp the file as
> long as it's not too big" or "becareful not to slurp a
> really big file or you'll be in trouble".
I'd like to add that some of it depends on swap space. I've slurped
well past physical me
> On Jan 22, 2004, at 12:18 PM, Dan Muey wrote:
>
> > There are always comments like "you can slurp the file as
> long as it's
> > not too big" or "becareful not to slurp a really big file
> or you'll be
> > in trouble".
> >
> > So what I'd like to survey is what would be what the safest
> ma
On Jan 22, 2004, at 12:18 PM, Dan Muey wrote:
There are always comments like "you can slurp the file as
long as it's not too big" or "becareful not to slurp a
really big file or you'll be in trouble".
So what I'd like to survey is what would be what the safest
max size of a file that one should ev
17 matches
Mail list logo
