Hi Team,
yes re-factoring is king!
When you stop for i.e. Catalina nice (Catalina stop) then
the current cache status will be saved onto disk. So the
old status is available at the next restart.
With 200 objects in cache, it still shutdowns very quick!
Maybe we can handle kill and ctrl-c in the
Hi,
sorry for being rough yesterday. That wasn't fair!
>From: Britton, Colin [mailto:[EMAIL PROTECTED]]
>
>Thanks for the work on the store. I think with the dispose option to put
>the store onto disk at shutdown that will work well, although the
>machine could spend a long time shutting down if
Thanks for the work on the store. I think with the dispose option to put
the store onto disk at shutdown that will work well, although the
machine could spend a long time shutting down if you have a lot of
objects in memory. I like the MRU store as I can throw lots of RAM at
serving from cache (an
Hi!
> BTW: How would you implement this? The filenames are not
> the same as the requested pages. They are parts of
> the xml serialization.
There should be defined some set of rules for apache to
determine how to extract/generate filename from an url,
and how to get known if it should check
Hi,
>From: Vadim Gritsenko [mailto:[EMAIL PROTECTED]]
>
>> From: Gerhard Froehlich [mailto:[EMAIL PROTECTED]]
>>
>> >New store implementation - does it swaps to file system when removing
>> >items from the stores?
>>
>> Yep it does. When the free() method is called, the oldest object is
>> swap
> From: Gerhard Froehlich [mailto:[EMAIL PROTECTED]]
>
> >New store implementation - does it swaps to file system when removing
> >items from the stores?
>
> Yep it does. When the free() method is called, the oldest object is
swapped
> to Filsystem. That's the main difference here.
Good!
> >>
Hi,
>From: Mikhail Fedotov [mailto:[EMAIL PROTECTED]]
>
>> a) The old way stored every object twice. First in
>> Memory, Second on the
>> Filesystem. That was a very _expensive_ operation. We
>> needed an extra
>> thread which did all that serialization and he eated
>> performance.
>> The onl
Hi!
Hi!
> a) The old way stored every object twice. First in
> Memory, Second on the
> Filesystem. That was a very _expensive_ operation. We
> needed an extra
> thread which did all that serialization and he eated
> performance.
> The only real advantage was to have the objects
> persistent
8, 2002 5:59 PM
>> >To: [EMAIL PROTECTED]
>> >Subject: RE: cvs commit: MRUMemoryStore.java
>FilesystemQueueObject.java
>> >
>> >
>> >For our application I want to not only cache from memory, but also
>store
>> >the objects on the fileSyste
> From: Gerhard Froehlich [mailto:[EMAIL PROTECTED]]
>
> Hi,
>
> >-Original Message-
> >From: Britton, Colin [mailto:[EMAIL PROTECTED]]
> >Sent: Monday, January 28, 2002 5:59 PM
> >To: [EMAIL PROTECTED]
> >Subject: RE: cvs commit: MRUM
Hi,
>-Original Message-
>From: Britton, Colin [mailto:[EMAIL PROTECTED]]
>Sent: Monday, January 28, 2002 5:59 PM
>To: [EMAIL PROTECTED]
>Subject: RE: cvs commit: MRUMemoryStore.java FilesystemQueueObject.java
>
>
>For our application I want to not only cache fro
For our application I want to not only cache from memory, but also store
the objects on the fileSystem (as the cost of generation in our app can
be high). With the change so that items are only written to the file
system when the number of memory objects reaches max and this.free() is
called it se
12 matches
Mail list logo
