On Thursday 10 April 2014 04:32:42 nginxsantos wrote:
> Thank you.
> But, my question is when we are allocating a pool of more than one page size
> why are we putting the max value as one page size and then further leading
> to memory allocation.
>
Because there are no advantages in allocating bi
Thank you.
But, my question is when we are allocating a pool of more than one page size
why are we putting the max value as one page size and then further leading
to memory allocation.
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,249161,249189#msg-249189
_
On Wed, Apr 09, 2014 at 08:31:29AM -0400, nginxsantos wrote:
> Suppose, I am allocating a pool of greater than 4k(page size). Say for
> example I am calling the function ngx_create_pool with 8096.
> But, this function will set the max as 4095 even if it has allocated 8K. Not
> sure, why is it being
Any expert opinions???
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,249161,249185#msg-249185
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
On Wednesday 09 April 2014 08:22:10 nginxsantos wrote:
> Thank you for the reply.
>
> I know it is simple. But, will we not get more performance benefit if we
> create the pools before hand. Say I will create a memory pool for the
> connections (for example say with 4000 entrie
Suppose, I am allocating a pool of greater than 4k(page size). Say for
example I am calling the function ngx_create_pool with 8096.
But, this function will set the max as 4095 even if it has allocated 8K. Not
sure, why is it being done like this.
p->max = (size < NGX_MAX_ALLOC_FROM_POOL) ? siz
Thank you for the reply.
I know it is simple. But, will we not get more performance benefit if we
create the pools before hand. Say I will create a memory pool for the
connections (for example say with 4000 entries). Everytime I need one, I
will go and get it from that pool and when I free it, I
On Wednesday 09 April 2014 04:55:42 nginxsantos wrote:
> Nginx when it accepts a connection, it creates a memory pool for that
> connection (allocating from heap). After which further memory requirement
> for that connection will be allocated from that pool. This is good.
> But, why
Also I noticed that initially for a connection, it allocates a pool of size
256 and if that exceeds, it goes and calls ngx_palloc_large which in turn
calls malloc.
So, can we not allocate more in the first attempt.
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,249144,249149#msg-249149
Nginx when it accepts a connection, it creates a memory pool for that
connection (allocating from heap). After which further memory requirement
for that connection will be allocated from that pool. This is good.
But, why don't we pre create the memory pools depending upon the numb
10 matches
Mail list logo
