On Tue, Nov 17, 2009 at 6:25 PM, Jason Edgecombe wrote:
> Derrick Brashear wrote:
>
>> On Tue, Nov 17, 2009 at 5:09 PM, Jason Edgecombe
>> wrote:
>>
>>
>>> Hi Everyone,
>>>
>>> Our webserver has been brought to a crawl many times over the last few
>>> weeks. I suspect it's an AFS bottleneck somew
On 8/14/07, Jeffrey Altman <[EMAIL PROTECTED]> wrote:
> Nate Gordon wrote:
> > So I loaded up ntop and isolated http, dns, ssh, afs, and mysql. I
> > ran the previous test (ab -k -c -t 120 ) again for
> > various numbers of users and here is what I came up with:
> &
accessing the afs cache.
If I can do further diagnostics/testing let me know.
On 8/13/07, Russ Allbery <[EMAIL PROTECTED]> wrote:
> "Nate Gordon" <[EMAIL PROTECTED]> writes:
>
> > I've looked through it before, but I usually get too annoyed when the
> > a
On 8/13/07, Russ Allbery <[EMAIL PROTECTED]> wrote:
> That -daemons value is way too high and will cause a ton of context
> switches, so that isn't what you want. However, it sounded like you'd
> already tried tweaking that. See the afsd man page:
>
>The default number of background daem
all.
On 8/13/07, Jason Edgecombe <[EMAIL PROTECTED]> wrote:
> Hi,
>
> Have you tried tinkering with the chunksize value? It's specified when
> afsd is run and tells the client how big of a chunk of each file to request.
>
> Jason
>
> Nate Gordon wrote:
> > So
r with lots and
lots of small file operations?
With the start of classes coming up soon this will mostly likely cause
my server to do very bad things on a very regular basis. I'm willing
to contemplate any idea at least once.
On 7/27/07, Nate Gordon <[EMAIL PROTECTED]> wrote:
>
> This shows me exactly what I would expect to happen in on the server.
> Aggregate requests per second reach a peak performance level which
> increases the individual request time.
The one thing I forgot to mention is that while arla is being hammered
the context switches cap out at around 1500/s
So I'm finally getting around to querying about some issues I've been
having for a long time with openafs 1.4.4 on rhel (3|4|5). In short,
the performance of my webservers serving up PHP code is less than
stellar in some cases. Those cases being defined as the requests per
second getting above 30
adversely
affect my servers.
On 7/11/07, Nate Gordon <[EMAIL PROTECTED]> wrote:
I'm currently trying to debug some mysterious server crashes and am
curious about how the sysctl var afs.GCPAGs works. From what I've
gleaned from the archives/code is that GCPAGs = 1 allows the garba
I'm currently trying to debug some mysterious server crashes and am
curious about how the sysctl var afs.GCPAGs works. From what I've
gleaned from the archives/code is that GCPAGs = 1 allows the garbage
collection of pags, anything else prevents it. Is this correct? Next
why would my GCPAGs be
10 matches
Mail list logo
