Am 29.02.2012 um 09:10 schrieb Sven Van Caekenberghe:
> Norbert,
>
> On 28 Feb 2012, at 21:30, Norbert Hartl wrote:
>
>> The only limit that I tested is a maximum of threads of 1100 or 1400, can't
>> remember right now. The image is stuck then.
>
> I know we are way off topic, but are you sur
On Wed, Feb 29, 2012 at 4:24 AM, Yanni Chiu wrote:
> On 28/02/12 4:30 PM, Mariano Martinez Peck wrote:
>
>>
>> If I understand you correctly, then what you are talking about is not
>> caching objects but rather lazy loading. You mean when Glorp lets some
>> proxies of the loaded graph so that the
Norbert,
On 28 Feb 2012, at 21:30, Norbert Hartl wrote:
> The only limit that I tested is a maximum of threads of 1100 or 1400, can't
> remember right now. The image is stuck then.
I know we are way off topic, but are you sure you were not running into some OS
limit (max open files/sockets whi
On 28/02/12 4:30 PM, Mariano Martinez Peck wrote:
If I understand you correctly, then what you are talking about is not
caching objects but rather lazy loading. You mean when Glorp lets some
proxies of the loaded graph so that they can load the rest of the graph
later on?
Okay, the concept I m
On 28/02/12 6:20 PM, Norbert Hartl wrote:
Uh, sorry for getting _slightly_ verbose and off-topic :)
Thanks for the informative answer. It's good to learn how others tackle
problems, and why they chose their solution.
Am 28.02.2012 um 22:09 schrieb Yanni Chiu:
> On 28/02/12 3:30 PM, Norbert Hartl wrote:
>>
>> I'm sorry that's all. I just started to do deployments with pharo
>> lately. I was doing everything in gemstone until 2 month ago.
>
> That's interesting. Have you moved everything to Pharo, or is some
On Tue, Feb 28, 2012 at 9:46 PM, Yanni Chiu wrote:
> On 28/02/12 2:48 PM, Mariano Martinez Peck wrote:
>
>>
>> Yes, object caching is NOT a problem itself, it is a feature of Glorp or
>> whatever. If what you use (like Fuel) is slow, then it may require some
>> tunning. It can be caching object o
On 28/02/12 3:30 PM, Norbert Hartl wrote:
I'm sorry that's all. I just started to do deployments with pharo
lately. I was doing everything in gemstone until 2 month ago.
That's interesting. Have you moved everything to Pharo, or is some part
still in GemStone? Can you outline why GemStone was
On 28 Feb 2012, at 21:30, Norbert Hartl wrote:
> Am 28.02.2012 um 20:35 schrieb Sven Van Caekenberghe:
>
>> Norbert,
>>
>> On 28 Feb 2012, at 17:32, Norbert Hartl wrote:
>>
>>> I experience image corruption with big images.
>>
>> I am assuming you are using a normal image on a 32-bit Cog VM o
On 28/02/12 2:48 PM, Mariano Martinez Peck wrote:
Yes, object caching is NOT a problem itself, it is a feature of Glorp or
whatever. If what you use (like Fuel) is slow, then it may require some
tunning. It can be caching object or not. What I suggest is that you
stress your system with big data
Am 28.02.2012 um 20:35 schrieb Sven Van Caekenberghe:
> Norbert,
>
> On 28 Feb 2012, at 17:32, Norbert Hartl wrote:
>
>> I experience image corruption with big images.
>
> I am assuming you are using a normal image on a 32-bit Cog VM on Linux ?
>
yes
> I am very interested in the practical l
On Tue, Feb 28, 2012 at 7:15 PM, Yanni Chiu wrote:
> On 28/02/12 11:03 AM, Norbert Hartl wrote:
>
>>
>> I first used image persistence but the image grow to large. Then I added
>> fuel as journal to be written before image save in order to be able to
>> recover from an emergency.
>> Now we redo t
Norbert,
On 28 Feb 2012, at 17:32, Norbert Hartl wrote:
> I experience image corruption with big images.
I am assuming you are using a normal image on a 32-bit Cog VM on Linux ?
I am very interested in the practical limits on image size (not necessarily
saving it).
What vm switches did you ap
Am 28.02.2012 um 19:15 schrieb Yanni Chiu:
> On 28/02/12 11:03 AM, Norbert Hartl wrote:
>>
>> I first used image persistence but the image grow to large. Then I added
>> fuel as journal to be written before image save in order to be able to
>> recover from an emergency.
>> Now we redo the persis
On 28/02/12 11:03 AM, Norbert Hartl wrote:
I first used image persistence but the image grow to large. Then I added
fuel as journal to be written before image save in order to be able to
recover from an emergency.
Now we redo the persistence part. An account object graph is dissected
into config
Am 28.02.2012 um 17:23 schrieb Mariano Martinez Peck:
>
>
> On Tue, Feb 28, 2012 at 5:03 PM, Norbert Hartl wrote:
>
> Am 28.02.2012 um 16:41 schrieb Mariano Martinez Peck:
>
>> Of course, not the fuel you use to go to work every day ;) I am talking
>> about Fuel serializer.
>> In particula
On 28 Feb 2012, at 17:03, Norbert Hartl wrote:
> Am 28.02.2012 um 16:41 schrieb Mariano Martinez Peck:
>
>> Of course, not the fuel you use to go to work every day ;) I am talking
>> about Fuel serializer.
>> In particular, I wonder if our page deserves an update:
>> rmod.lille.inria.fr/web/p
On Tue, Feb 28, 2012 at 5:03 PM, Norbert Hartl wrote:
>
> Am 28.02.2012 um 16:41 schrieb Mariano Martinez Peck:
>
> Of course, not the fuel you use to go to work every day ;) I am talking
> about Fuel serializer.
> In particular, I wonder if our page deserves an update:
> rmod.lille.inria.fr/web
Am 28.02.2012 um 16:41 schrieb Mariano Martinez Peck:
> Of course, not the fuel you use to go to work every day ;) I am talking
> about Fuel serializer.
> In particular, I wonder if our page deserves an update:
> rmod.lille.inria.fr/web/pier/software/Fuel/Software-using-Fuel
>
> Let me know i
19 matches
Mail list logo
