Great! I'm not sure what you mean by "a copy of the jar file" but we'd
of course like to see the source, not just the binaries.
The student must explicitly indicate that he is handing over the code to
the ASF. The normal way this is done is to create a JIRA item (our bug
tracking system) and then put the changes he's made as an attachment to
this JIRA item, indicating he is granting the code to the ASF. I'd be
happy to help guide the student through this process. Better yet, we
should have one of our store experts work with the student to look at
getting his code in. Any volunteers?
David
Darcy Benoit wrote:
I had a student implement an in-memory version of Derby for his honours
thesis. I am under the impression that the code is just about ready to
submit to the code tree. I can get you a copy of the jar file with the
in-memory implementation if you want, but I am not sure that it has pass
the derby-all testing.
darcy
On Sat, 20 May 2006 14:44:25 -0300,
<[EMAIL PROTECTED]> wrote:
Date: Thu, 18 May 2006 10:40:42 -0700
From: David Van Couvering <[EMAIL PROTECTED]>
Subject: Re: High throughput, min durability - tuning
To: [email protected]
Cc: [email protected], ashwinjay <[EMAIL PROTECTED]>
Well, I have a couple of thoughts:
- Depending upon your OS, often the /tmp directory is actually mapped
to memory, not disk. You might
try putting your database in /tmp
- There has been a proposal and I think some work on implementing an
in-memory implementation of the
store interface. I would highly recommend you think about building
this yourself. There are experts
on the team who would be more than glad to guide you in this effort.
If nothing else you would learn
some of the itnernals really well which could only help you in your
efforts to tune the system.
David
--Dr. Darcy Benoit
http://cs.acadiau.ca/~dbenoit/
