2011/11/19 Raffaele P. Guidi :
> We could also provide a high performance serializer/deserializer based on
> protostuff... but, in any case let's follow the simplest path to
> demonstrate the case, there will always be room for improvement. I'm sure
> Mir will show us something as soon as it will b
We could also provide a high performance serializer/deserializer based on
protostuff... but, in any case let's follow the simplest path to
demonstrate the case, there will always be room for improvement. I'm sure
Mir will show us something as soon as it will be ready... I used to put
stuff in githu
On 19.11.11 09:43, Raffaele P. Guidi wrote:
> It depends on what JCS requires to manage. If it handles the key-value
> mapping on its own (as I suppose it does) you shouldn't need to use DM's
> CacheService (it would be a waste of memory) which does the same.
> CacheService puts KV mapping on top
It depends on what JCS requires to manage. If it handles the key-value
mapping on its own (as I suppose it does) you shouldn't need to use DM's
CacheService (it would be a waste of memory) which does the same.
CacheService puts KV mapping on top of MemoryStorageService (and some more
things such a
Hi Everyone, after looking into the DirectMemory code, I figured that
instead of using MemoryManagerService, I can directly use the CacheService
interface. The CacheServiceImpl class seems to do almost all the work. So I
am thinking why rewrite the same code? What do you think?
-Mir
On Thu, Nov 1
Mir (in cc) volounteered on this task - I think he could start following
your advice to use IndexDiskCache as a template and try to implement it on
top of our MemoryManagerService. I suggest Mir and I subscribe to the
commons mailing lists (I already did) and Thomas (and anyone interested)
subscrib
On 09.11.11 00:10, Raffaele P. Guidi wrote:
> This is not so different from an indexed file, just it is in memory - maybe
> you could take a look at the code (which is fairly simple) and get back to
> us with some more targeted questions.
I understand that the plugin is supposed to be added as an
Cool. Basically the plugin should fit in the middle between standard heap
cache and the lateral (network) plugin. DirectMemory exposes two basic
services: the memorystorage, which acts almost like a malloc(), allocating
large buffers which can be split in "slices" described by a Pointer
structure (
On 08.11.11 20:59, Raffaele P. Guidi wrote:
> Are you guys interested in merging efforts on this?
Yes, absolutely. I, however, would need some introduction into the
subject to understand how this is supposed to work. I can assure my
support for the integration into the JCS code.
Bye, Thomas.
-
Hi, we discussed on our mailing list about integrating DirectMemory (which
has recently begun incubation [1]) as a JCS off-heap plugin. We find that
this could be more profitable, for us and the community in the whole, than
spending time and effort building DirectMemory as a fully featured cache,
a
10 matches
Mail list logo
