Bulk fetches. GC competition

For my load profile I got following results:

Java 6 (CMS wins, ParallelOld looses):

Java 7 (G1 wins, ParallelOld looses):

Interestingly, flushing object from cache after “fetch”, i.e.

if (_iterator.hasNext()) {
    IDfPersistentObject object = _iterator.next();
    try {
        _session.flushObject(object.getObjectId());
    } catch (DfException ex) {
        throw new RuntimeException(ex);
    }
    return;
}

improve results by 20% percent:

Because my load profile is not typical for any DFC application, I decided to perform same benchmarks for regular fetches, i.e. session.getObject() – I suppose such load is typical for BPM, DFS and REST, unfortunately, content server is so slow in performing sysobject fetches that it is hardly possible to notice a significant difference between garbage collectors:

So, I decided to switch to non-sysobject objects. Stay tuned.

2 thoughts on “Bulk fetches. GC competition

  1. Pingback: Simple fetches. GC competition | Documentum in a (nuts)HELL
  2. Pingback: What happens when smart guy does not sit back | Documentum in a (nuts)HELL

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s