gaspersic/java-design-patterns
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
9ec0935a1c
java-design-patterns/object-pool
History
Ilkka Seppälä 9ec0935a1c Merge pull request from leogtzr/master 
Adding initialization-on-demand idiom and noninstantiable class instead of interface constant idiom
2017-01-23 08:21:07 +02:00
..
etc
Update URM Version to 1.4.4 and regenerated all puml files
2016-11-26 12:51:06 +01:00
src
Changing code to use interfaces instead of implementations.
2017-01-21 15:47:54 -07:00
pom.xml
Set version for next development iteration
2016-12-31 10:24:26 +02:00
README.md
Work on : Commit initial pumlId's added by the script
2016-08-30 15:10:34 +02:00

README.md

layout, title, folder, permalink, pumlid, categories, tags
layout title folder permalink pumlid categories tags
pattern Object Pool object-pool /patterns/object-pool/ JSV94SCm2030Lk829Fxf1cF6bWU1XYDkFtdcjxiD9Qc3o-LrPQvu0pW-_HnvrLx1JgR9cfrimf1wCD7XnW-sWsESsXPcicl0nFW1RB-PiYqp0KxwVo-VVTMKBm00 Creational
Java
Difficulty-Beginner
Performance

Intent

When objects are expensive to create and they are needed only for short periods of time it is advantageous to utilize the Object Pool pattern. The Object Pool provides a cache for instantiated objects tracking which ones are in use and which are available.

alt text

Applicability

Use the Object Pool pattern when

  • the objects are expensive to create (allocation cost)
  • you need a large number of short-lived objects (memory fragmentation)