Upper limit on size of cached objects

Poster Content
nk4um User
Posts: 39
November 8, 2011 18:16

Thanks Peter and Tony, that's what I was assuming. It's good news for me.

Glenn.

Like · Post Reply
nk4um Administrator
Posts: 607
November 8, 2011 16:34NetKernel can't use representation size

In NetKernel we keep all the cached representations in their native objects and they are not serialized. Unfortunately in Java their is no way, no portable and efficient way at least, in determining the true size of object graphs. Because of this we don't use this metric in cache operation.

Cheers, Tony

Like · Post Reply
nk4um Moderator
Posts: 901
November 8, 2011 16:05

There is no limit. The cache will start to GC the least valuable reps when the heap size gets within a threshold level (see the kernel configuration - I think the default is 15% of heap free). So the more heap you have the bigger the stuff you can cache. But there are no fundamental limits.

Like · Post Reply
nk4um User
Posts: 39
November 8, 2011 15:06Upper limit on size of cached objects

Does NK have an upper limit on the size of representations which will be cached? I know, for example, that memcached has a 1Mb limit on individual objects.

Note that I'm talking about the size of individual representations, not the size of the cache itself - although I would assume that an object that's on its own bigger than the maximum cache size won't be cached ...

Glenn.

Like · Post Reply