[33101] in Perl-Users-Digest
Perl-Users Digest, Issue: 4377 Volume: 11
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Mon Feb 23 11:09:16 2015
Date: Mon, 23 Feb 2015 08:09:03 -0800 (PST)
From: Perl-Users Digest <Perl-Users-Request@ruby.OCE.ORST.EDU>
To: Perl-Users@ruby.OCE.ORST.EDU (Perl-Users Digest)
Perl-Users Digest Mon, 23 Feb 2015 Volume: 11 Number: 4377
Today's topics:
Re: Poor man's "object", and question on regex capture <rweikusat@mobileactivedefense.com>
Re: Traversing through sub dirs and read file contents <m@rtij.nl.invlalid>
Re: Traversing through sub dirs and read file contents <rweikusat@mobileactivedefense.com>
Re: Traversing through sub dirs and read file contents <m@rtij.nl.invlalid>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Mon, 23 Feb 2015 15:32:05 +0000
From: Rainer Weikusat <rweikusat@mobileactivedefense.com>
Subject: Re: Poor man's "object", and question on regex capture list.
Message-Id: <87egpgzlsa.fsf@doppelsaurus.mobileactivedefense.com>
"Peter J. Holzer" <hjp-usenet3@hjp.at> writes:
> On 2015-02-21 08:13, Robbie Hatley <see.my.sig@for.my.address> wrote:
[...]
> the Moose way (which is sort of becoming the new standard way, but as
> Wikipedia informs me, some Moose can weigh up to 725 kg, so that's a
> rather heavyweight solution):
There are other interesting comparisons here: Camels are animals very
well adapted to living in 'desert' conditions and have been highly
useful as domesticated animals for more than 3000 years. Mooses are
impressively massive, don't really do anything but eat and reproduce,
and accidentally running into one with a 'standard' passenger car
provides an interesting option of getting oneself killed as the car will
smash through the legs of the animal whose body will then drop onto the
windshield, crushing that an any persons unfortunate enough to be
sitting in the front seats.
------------------------------
Date: Mon, 23 Feb 2015 15:22:49 +0100
From: Martijn Lievaart <m@rtij.nl.invlalid>
Subject: Re: Traversing through sub dirs and read file contents
Message-Id: <pmprrb-umh.ln1@news.rtij.nl>
On Sun, 22 Feb 2015 18:34:46 +0000, Tim McDaniel wrote:
> In article <fu5tqb-3lm.ln1@news.rtij.nl>,
> Martijn Lievaart <m@rtij.nl.invlalid> wrote:
>>On Wed, 11 Feb 2015 21:58:47 +0100, Peter J. Holzer wrote:
>>
>>> That depends on what the OP means by "a lot of files". Hundreds?
>>> Thousands? Tens of thousands? Millions? Billions? Probably hundreds or
>>> thousands. And it probably doesn't matter unless we get into at least
>>> the 100k to 1M files per directory range, possibly even higher.
>>
>>As a side note, current file systems may handle that many files in a
>>directory gracefully, but maybe not.
>
> Exemplia gratia: I *very occasionally* run P4V, a GUI front-end for
> Perforce. [1] The problems:
> - the one thing that isn't fast is the network latency
> - one of the
> directories has a bazillion directories and files, and is
> the parent of most of the source tree
Sorry, but this falls in the category "Don't do that then!"
Either:
- Rearrange the files, bring some sanity
- Use a better protocol than CIFS/SMB
- Run P4V on a machine closer to the files (less latency)
- Use some form of WAN acceleration.
M4
------------------------------
Date: Mon, 23 Feb 2015 15:02:02 +0000
From: Rainer Weikusat <rweikusat@mobileactivedefense.com>
Subject: Re: Traversing through sub dirs and read file contents
Message-Id: <87r3tgzn6d.fsf@doppelsaurus.mobileactivedefense.com>
Martijn Lievaart <m@rtij.nl.invlalid> writes:
> On Sun, 22 Feb 2015 18:34:46 +0000, Tim McDaniel wrote:
>> In article <fu5tqb-3lm.ln1@news.rtij.nl>,
>> Martijn Lievaart <m@rtij.nl.invlalid> wrote:
>>>On Wed, 11 Feb 2015 21:58:47 +0100, Peter J. Holzer wrote:
>>>
>>>> That depends on what the OP means by "a lot of files". Hundreds?
>>>> Thousands? Tens of thousands? Millions? Billions? Probably hundreds or
>>>> thousands. And it probably doesn't matter unless we get into at least
>>>> the 100k to 1M files per directory range, possibly even higher.
>>>
>>>As a side note, current file systems may handle that many files in a
>>>directory gracefully, but maybe not.
>>
>> Exemplia gratia: I *very occasionally* run P4V, a GUI front-end for
>> Perforce. [1] The problems:
>> - the one thing that isn't fast is the network latency
>> - one of the
>> directories has a bazillion directories and files, and is
>> the parent of most of the source tree
>
> Sorry, but this falls in the category "Don't do that then!"
>
> Either:
> - Rearrange the files, bring some sanity
> - Use a better protocol than CIFS/SMB
> - Run P4V on a machine closer to the files (less latency)
> - Use some form of WAN acceleration.
All of this amounts to nothing but 'change the environment such that
assumptions coded into the software are less wrong'.
------------------------------
Date: Mon, 23 Feb 2015 16:24:48 +0100
From: Martijn Lievaart <m@rtij.nl.invlalid>
Subject: Re: Traversing through sub dirs and read file contents
Message-Id: <0btrrb-umh.ln1@news.rtij.nl>
On Mon, 23 Feb 2015 15:02:02 +0000, Rainer Weikusat wrote:
> Martijn Lievaart <m@rtij.nl.invlalid> writes:
>> On Sun, 22 Feb 2015 18:34:46 +0000, Tim McDaniel wrote:
>>> In article <fu5tqb-3lm.ln1@news.rtij.nl>,
>>> Martijn Lievaart <m@rtij.nl.invlalid> wrote:
>>>>On Wed, 11 Feb 2015 21:58:47 +0100, Peter J. Holzer wrote:
>>>>
>>>>> That depends on what the OP means by "a lot of files". Hundreds?
>>>>> Thousands? Tens of thousands? Millions? Billions? Probably hundreds
>>>>> or thousands. And it probably doesn't matter unless we get into at
>>>>> least the 100k to 1M files per directory range, possibly even
>>>>> higher.
>>>>
>>>>As a side note, current file systems may handle that many files in a
>>>>directory gracefully, but maybe not.
>>>
>>> Exemplia gratia: I *very occasionally* run P4V, a GUI front-end for
>>> Perforce. [1] The problems:
>>> - the one thing that isn't fast is the network latency - one of the
>>> directories has a bazillion directories and files, and is
>>> the parent of most of the source tree
>>
>> Sorry, but this falls in the category "Don't do that then!"
>>
>> Either:
>> - Rearrange the files, bring some sanity - Use a better protocol than
>> CIFS/SMB - Run P4V on a machine closer to the files (less latency) -
>> Use some form of WAN acceleration.
>
> All of this amounts to nothing but 'change the environment such that
> assumptions coded into the software are less wrong'.
No. Even if the software behaviour is slightly moronic, there is not much
P4V can do about a pathetic setup. Doing a ls will trigger the same
behaviour.
Repeat after me: I will not run CIFS/SMB over high latency networks
unless I know what I'm doing (or am in desperate need of coffee).
M4
------------------------------
Date: 6 Apr 2001 21:33:47 GMT (Last modified)
From: Perl-Users-Request@ruby.oce.orst.edu (Perl-Users-Digest Admin)
Subject: Digest Administrivia (Last modified: 6 Apr 01)
Message-Id: <null>
Administrivia:
To submit articles to comp.lang.perl.announce, send your article to
clpa@perl.com.
Back issues are available via anonymous ftp from
ftp://cil-www.oce.orst.edu/pub/perl/old-digests.
#For other requests pertaining to the digest, send mail to
#perl-users-request@ruby.oce.orst.edu. Do not waste your time or mine
#sending perl questions to the -request address, I don't have time to
#answer them even if I did know the answer.
------------------------------
End of Perl-Users Digest V11 Issue 4377
***************************************
