On Thursday 07 May 2009 01:06:24 Dennis Nezic wrote:
> On Thu, 7 May 2009 00:23:37 +0100, Matthew Toseland wrote:
> > On Wednesday 06 May 2009 23:52:22 Juiceman wrote:
> > >
> > > On Wed, May 6, 2009 at 12:50 PM, Juiceman wrote:
> > > > On Wed, May 6, 2009 at 11:37 AM, Matthew Toseland
> > > > w
On Mon, May 11, 2009 at 4:27 PM, Matthew Toseland
wrote:
> On Thursday 07 May 2009 01:06:24 Dennis Nezic wrote:
>> On Thu, 7 May 2009 00:23:37 +0100, Matthew Toseland wrote:
>> > On Wednesday 06 May 2009 23:52:22 Juiceman wrote:
>> > >
>> > > On Wed, May 6, 2009 at 12:50 PM, Juiceman ?wrote:
>> >
On Mon, May 11, 2009 at 4:27 PM, Matthew Toseland
wrote:
> On Thursday 07 May 2009 01:06:24 Dennis Nezic wrote:
>> On Thu, 7 May 2009 00:23:37 +0100, Matthew Toseland wrote:
>> > On Wednesday 06 May 2009 23:52:22 Juiceman wrote:
>> > >
>> > > On Wed, May 6, 2009 at 12:50 PM, Juiceman wrote:
>> >
On Thursday 07 May 2009 01:06:24 Dennis Nezic wrote:
> On Thu, 7 May 2009 00:23:37 +0100, Matthew Toseland wrote:
> > On Wednesday 06 May 2009 23:52:22 Juiceman wrote:
> > >
> > > On Wed, May 6, 2009 at 12:50 PM, Juiceman wrote:
> > > > On Wed, May 6, 2009 at 11:37 AM, Matthew Toseland
> > > > w
On Wednesday 06 May 2009 23:52:22 Juiceman wrote:
>
> On Wed, May 6, 2009 at 12:50 PM, Juiceman wrote:
> > On Wed, May 6, 2009 at 11:37 AM, Matthew Toseland
> > wrote:
> >> On Wednesday 06 May 2009 14:43:59 Victor Denisov wrote:
> >>> Matthew Toseland wrote:
> >>> > This is the downside of db4o.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> One other thing, for both you and Juiceman:
> How's the CPU usage? Given how much RAM you have I would expect node.db4o to
> be cached in memory (how big is it?). But doing a read through the OS to the
> OS disk cache may cost a lot of CPU (context
On Thu, 7 May 2009 00:23:37 +0100, Matthew Toseland wrote:
> On Wednesday 06 May 2009 23:52:22 Juiceman wrote:
> >
> > On Wed, May 6, 2009 at 12:50 PM, Juiceman wrote:
> > > On Wed, May 6, 2009 at 11:37 AM, Matthew Toseland
> > > wrote:
> > >> On Wednesday 06 May 2009 14:43:59 Victor Denisov wro
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, May 6, 2009 at 12:50 PM, Juiceman wrote:
> On Wed, May 6, 2009 at 11:37 AM, Matthew Toseland
> wrote:
>> On Wednesday 06 May 2009 14:43:59 Victor Denisov wrote:
>>> Matthew Toseland wrote:
>>> > This is the downside of db4o. If it is a wide
On Thu, 7 May 2009 00:23:37 +0100, Matthew Toseland wrote:
> On Wednesday 06 May 2009 23:52:22 Juiceman wrote:
> >
> > On Wed, May 6, 2009 at 12:50 PM, Juiceman wrote:
> > > On Wed, May 6, 2009 at 11:37 AM, Matthew Toseland
> > > wrote:
> > >> On Wednesday 06 May 2009 14:43:59 Victor Denisov wro
On Wednesday 06 May 2009 14:43:59 Victor Denisov wrote:
> Matthew Toseland wrote:
> > This is the downside of db4o. If it is a widespread problem, we're gonna
have
> > to revert it. Which means throwing away more than 6 months work largely
> > funded by Google's $18K.
>
> I think that using a dat
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, May 6, 2009 at 12:50 PM, Juiceman wrote:
> On Wed, May 6, 2009 at 11:37 AM, Matthew Toseland
> wrote:
>> On Wednesday 06 May 2009 14:43:59 Victor Denisov wrote:
>>> Matthew Toseland wrote:
>>> > This is the downside of db4o. If it is a wide
On Wed, May 6, 2009 at 11:37 AM, Matthew Toseland
wrote:
> On Wednesday 06 May 2009 14:43:59 Victor Denisov wrote:
>> Matthew Toseland wrote:
>> > This is the downside of db4o. If it is a widespread problem, we're gonna
> have
>> > to revert it. Which means throwing away more than 6 months work la
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> One other thing, for both you and Juiceman:
> How's the CPU usage? Given how much RAM you have I would expect node.db4o to
> be cached in memory (how big is it?). But doing a read through the OS to the
> OS disk cache may cost a lot of CPU (context
On Wed, May 6, 2009 at 11:37 AM, Matthew Toseland
wrote:
> On Wednesday 06 May 2009 14:43:59 Victor Denisov wrote:
>> Matthew Toseland wrote:
>> > This is the downside of db4o. If it is a widespread problem, we're gonna
> have
>> > to revert it. Which means throwing away more than 6 months work la
On Wednesday 06 May 2009 14:43:59 Victor Denisov wrote:
> Matthew Toseland wrote:
> > This is the downside of db4o. If it is a widespread problem, we're gonna
have
> > to revert it. Which means throwing away more than 6 months work largely
> > funded by Google's $18K.
>
> I think that using a dat
15 matches
Mail list logo