Closed GoogleCodeExporter closed 9 years ago
Original comment by rc...@library.rochester.edu
on 6 Aug 2009 at 5:31
As discussed in meeting today, need to derive a plan for this, more than just
adding
more memory. We need to have some directions created on how to parse out and
use
the available memory so that jobs don't just fail.
Also discussed that we need a plan for how to hand different scenarios, such as
the
number of harvests the OAI toolkit should respond to. For example, if multiple
harvest request come in at once, does the OAI Toolkit respond to all of them,
just
perhaps more slowly, or do we set a number based on certain conditions.
Original comment by rc...@library.rochester.edu
on 10 Aug 2009 at 5:31
Shrey will write the results and any advice in here and in the documentation re.
memory allocation and data set size. More testing for the handling of different
scenarios as mentioned above will need to be done in the future.
Original comment by rc...@library.rochester.edu
on 18 Feb 2010 at 4:44
Per C Delis, no longer an issue after rev. 145
Original comment by rc...@library.rochester.edu
on 11 May 2011 at 8:23
Original issue reported on code.google.com by
rc...@library.rochester.edu
on 5 Aug 2009 at 4:39