On Thursday 02 July 2015 11:27 AM, Krishnan Parthasarathi wrote:
Yes. The PROC_MAX is the maximum no. of 'worker' threads that would be spawned
for a given
syncenv.
- Original Message -
- Original Message -
From: "Krishnan Parthasarathi"
To: "Pranith Kumar Karampuri"
Cc:
- Original Message -
> From: "Krishnan Parthasarathi"
> To: "Raghavendra Gowdappa"
> Cc: "Pranith Kumar Karampuri" , "Vijay Bellur"
> , "Vijaikumar M"
> , "Gluster Devel" ,
> "Nagaprasad Sathyanarayana"
>
> Sent: Thursday, July 2, 2015 11:27:34 AM
> Subject: Re: Huge memory consumpti
Yes. The PROC_MAX is the maximum no. of 'worker' threads that would be spawned
for a given
syncenv.
- Original Message -
>
>
> - Original Message -
> > From: "Krishnan Parthasarathi"
> > To: "Pranith Kumar Karampuri"
> > Cc: "Vijay Bellur" , "Vijaikumar M"
> > , "Gluster Devel
- Original Message -
> From: "Krishnan Parthasarathi"
> To: "Pranith Kumar Karampuri"
> Cc: "Vijay Bellur" , "Vijaikumar M"
> , "Gluster Devel"
> , "Raghavendra Gowdappa" ,
> "Nagaprasad Sathyanarayana"
>
> Sent: Thursday, July 2, 2015 10:54:44 AM
> Subject: Re: Huge memory consumpti
Yes, we could take synctask size as an argument for synctask_create.
The increase in synctask threads is not really a problem, it can't
grow more than 16 (SYNCENV_PROC_MAX).
- Original Message -
>
>
> On 07/02/2015 10:40 AM, Krishnan Parthasarathi wrote:
> >
> > - Original Message --
On 07/02/2015 10:40 AM, Krishnan Parthasarathi wrote:
- Original Message -
On Wednesday 01 July 2015 08:41 AM, Vijaikumar M wrote:
Hi,
The new marker xlator uses syncop framework to update quota-size in the
background, it uses one synctask per write FOP.
If there are 100 parallel wr
- Original Message -
> On Wednesday 01 July 2015 08:41 AM, Vijaikumar M wrote:
> > Hi,
> >
> > The new marker xlator uses syncop framework to update quota-size in the
> > background, it uses one synctask per write FOP.
> > If there are 100 parallel writes with all different inodes but on
On Wednesday 01 July 2015 08:41 AM, Vijaikumar M wrote:
Hi,
The new marker xlator uses syncop framework to update quota-size in the
background, it uses one synctask per write FOP.
If there are 100 parallel writes with all different inodes but on the
same directory '/dir', there will be ~100 txn
Hi,
The new marker xlator uses syncop framework to update quota-size in the
background, it uses one synctask per write FOP.
If there are 100 parallel writes with all different inodes but on the
same directory '/dir', there will be ~100 txn waiting in queue to
acquire a lock on on its parent i.