Our Community is getting an upgrade! To get everything ready for the relaunch, we’ll be placing the site in read-only mode starting September 21st.
We really appreciate your understanding while we get things set up behind the scenes. Catch up on all the exciting details about the move here.
Need help or have questions? Drop us a line at [email protected]

Archives of Support Questions (Read Only)

This is an archived board for historical reference. Information and links may no longer be available or relevant
Announcements
This board is archived and read-only for historical reference. To ask a new question, please post a new topic on the appropriate active board.

Any recommendation on using G1GC over CMS GC for HBase?

avatar

What are advantages and benefits of G1GC? Any benchmarks?

1 ACCEPTED SOLUTION

avatar
Master Mentor

@Pardeep

Hope this helps

There are several good documents online.

Link

  • In CMS the young and old generation heap space are physically differentiated. But in the case of G1 they are logical. This is achieved by dividing the total heap space into number of regions (2000) and the regions are identified whether they belong to young or old space.
  • Compaction of the heap space is done as part of the collection process which was not the case in CMS.
  • G1 collector tries to meet user specified target for application pause time during the collection process.

View solution in original post

1 REPLY 1

avatar
Master Mentor

@Pardeep

Hope this helps

There are several good documents online.

Link

  • In CMS the young and old generation heap space are physically differentiated. But in the case of G1 they are logical. This is achieved by dividing the total heap space into number of regions (2000) and the regions are identified whether they belong to young or old space.
  • Compaction of the heap space is done as part of the collection process which was not the case in CMS.
  • G1 collector tries to meet user specified target for application pause time during the collection process.