Mark,
On 1/20/22 04:18, Mark Thomas wrote:
On 20/01/2022 08:54, Olaf Kock wrote:
My rule of thumb is: The
more memory there is to be claimed in GC, the longer a full GC run
takes.
Nope.
The time a GC run takes is proportional to the size of objects in memory
that do not need to be GC'd. G
Lance,
On 1/19/22 17:35, Campbell, Lance wrote:
On a Tomcat 9.x dedicated Linux server with 16G of memory, how much
memory would you allocate for the OS?
Assume there is no file processing taking place. Also assume Tomcat
is communicating primarily with a PostgreSQL database and Apache web
ser
Hi Mark
On 20.01.22 10:18, Mark Thomas wrote:
> On 20/01/2022 08:54, Olaf Kock wrote:
>
>> My rule of thumb is: The
>> more memory there is to be claimed in GC, the longer a full GC run
>> takes.
>
> Nope.
>
> The time a GC run takes is proportional to the size of objects in
> memory that do not
On 20/01/2022 08:54, Olaf Kock wrote:
My rule of thumb is: The
more memory there is to be claimed in GC, the longer a full GC run
takes.
Nope.
The time a GC run takes is proportional to the size of objects in memory
that do not need to be GC'd. GC walks the active object tree so it is
the
Hi Lance
On 19.01.22 23:35, Campbell, Lance wrote:
> On a Tomcat 9.x dedicated Linux server with 16G of memory, how much memory
> would you allocate for the OS?
>
> Assume there is no file processing taking place. Also assume Tomcat is
> communicating primarily with a PostgreSQL database and Ap
