Displaying 11 results from an estimated 11 matches for "53864".
Did you mean:
5386
2018 Jan 29
2
Run away memory with gluster mount
...link to the dumps. In the mean
time, I'm including the results of your above queries for the first
dump, the 18 hour dump, and the 36 hour dump:
# grep itable glusterdump.153904.dump.1517104561 | grep active | wc -l
53865
# grep itable glusterdump.153904.dump.1517169361 | grep active | wc -l
53864
# grep itable glusterdump.153904.dump.1517234161 | grep active | wc -l
53864
# grep itable glusterdump.153904.dump.1517104561 | grep active_size
xlator.mount.fuse.itable.active_size=53864
# grep itable glusterdump.153904.dump.1517169361 | grep active_size
xlator.mount.fuse.itable.active_size=53863...
2018 Jan 30
1
Run away memory with gluster mount
...t; time, I'm including the results of your above queries for the first
> dump, the 18 hour dump, and the 36 hour dump:
>
> # grep itable glusterdump.153904.dump.1517104561 | grep active | wc -l
> 53865
> # grep itable glusterdump.153904.dump.1517169361 | grep active | wc -l
> 53864
> # grep itable glusterdump.153904.dump.1517234161 | grep active | wc -l
> 53864
>
> # grep itable glusterdump.153904.dump.1517104561 | grep active_size
> xlator.mount.fuse.itable.active_size=53864
> # grep itable glusterdump.153904.dump.1517169361 | grep active_size
> xlator....
2018 Feb 02
3
Run away memory with gluster mount
...above queries for the first
>>> dump, the 18 hour dump, and the 36 hour dump:
>>>
>>> # grep itable glusterdump.153904.dump.1517104561 | grep active | wc -l
>>> 53865
>>> # grep itable glusterdump.153904.dump.1517169361 | grep active | wc -l
>>> 53864
>>> # grep itable glusterdump.153904.dump.1517234161 | grep active | wc -l
>>> 53864
>>>
>>> # grep itable glusterdump.153904.dump.1517104561 | grep active_size
>>> xlator.mount.fuse.itable.active_size=53864
>>> # grep itable glusterdump.153904....
2018 Feb 01
0
Run away memory with gluster mount
...ing the results of your above queries for the first
>> dump, the 18 hour dump, and the 36 hour dump:
>>
>> # grep itable glusterdump.153904.dump.1517104561 | grep active | wc -l
>> 53865
>> # grep itable glusterdump.153904.dump.1517169361 | grep active | wc -l
>> 53864
>> # grep itable glusterdump.153904.dump.1517234161 | grep active | wc -l
>> 53864
>>
>> # grep itable glusterdump.153904.dump.1517104561 | grep active_size
>> xlator.mount.fuse.itable.active_size=53864
>> # grep itable glusterdump.153904.dump.1517169361 | grep a...
2018 Feb 03
0
Run away memory with gluster mount
...mp, the 18 hour dump, and the 36 hour dump:
>
> # grep itable glusterdump.153904.dump.1517104561 | grep
> active | wc -l
> 53865
> # grep itable glusterdump.153904.dump.1517169361 | grep
> active | wc -l
> 53864
> # grep itable glusterdump.153904.dump.1517234161 | grep
> active | wc -l
> 53864
>
> # grep itable glusterdump.153904.dump.1517104561 | grep
> active_size
> xlator.mount.fuse.itable.active_size=53864
>...
2018 Feb 21
1
Run away memory with gluster mount
...he 36 hour dump:
>>
>> ??????????? # grep itable glusterdump.153904.dump.1517104561 | grep
>> ??????????? active | wc -l
>> ??????????? 53865
>> ??????????? # grep itable glusterdump.153904.dump.1517169361 | grep
>> ??????????? active | wc -l
>> ??????????? 53864
>> ??????????? # grep itable glusterdump.153904.dump.1517234161 | grep
>> ??????????? active | wc -l
>> ??????????? 53864
>>
>> ??????????? # grep itable glusterdump.153904.dump.1517104561 | grep
>> ??????????? active_size
>> ??????????? xlator.mount.fuse.i...
2018 Feb 05
1
Run away memory with gluster mount
...ur dump:
> >
> > # grep itable glusterdump.153904.dump.1517104561 | grep
> > active | wc -l
> > 53865
> > # grep itable glusterdump.153904.dump.1517169361 | grep
> > active | wc -l
> > 53864
> > # grep itable glusterdump.153904.dump.1517234161 | grep
> > active | wc -l
> > 53864
> >
> > # grep itable glusterdump.153904.dump.1517104561 | grep
> > active_size
> > xlator.moun...
2018 Jan 29
0
Run away memory with gluster mount
----- Original Message -----
> From: "Ravishankar N" <ravishankar at redhat.com>
> To: "Dan Ragle" <daniel at Biblestuph.com>, gluster-users at gluster.org
> Cc: "Csaba Henk" <chenk at redhat.com>, "Niels de Vos" <ndevos at redhat.com>, "Nithya Balachandran" <nbalacha at redhat.com>,
> "Raghavendra
2018 Jan 27
6
Run away memory with gluster mount
On 01/27/2018 02:29 AM, Dan Ragle wrote:
>
> On 1/25/2018 8:21 PM, Ravishankar N wrote:
>>
>>
>> On 01/25/2018 11:04 PM, Dan Ragle wrote:
>>> *sigh* trying again to correct formatting ... apologize for the
>>> earlier mess.
>>>
>>> Having a memory issue with Gluster 3.12.4 and not sure how to
>>> troubleshoot. I don't
2013 Dec 23
2
[PATCH net-next 3/3] net: auto-tune mergeable rx buffer size for improved performance
On Mon, Dec 16, 2013 at 04:16:29PM -0800, Michael Dalton wrote:
> Commit 2613af0ed18a ("virtio_net: migrate mergeable rx buffers to page frag
> allocators") changed the mergeable receive buffer size from PAGE_SIZE to
> MTU-size, introducing a single-stream regression for benchmarks with large
> average packet size. There is no single optimal buffer size for all
>
2013 Dec 23
2
[PATCH net-next 3/3] net: auto-tune mergeable rx buffer size for improved performance
On Mon, Dec 16, 2013 at 04:16:29PM -0800, Michael Dalton wrote:
> Commit 2613af0ed18a ("virtio_net: migrate mergeable rx buffers to page frag
> allocators") changed the mergeable receive buffer size from PAGE_SIZE to
> MTU-size, introducing a single-stream regression for benchmarks with large
> average packet size. There is no single optimal buffer size for all
>