| div |
|---|
|
| div |
|---|
| | Table of Contents |
|---|
| maxLevel | 2 |
|---|
| indent | 8px |
|---|
| style | none |
|---|
|
|
|
Overview
| Excerpt |
|---|
Talon supports zero garbage steady state operation for |
application applications that run with Event Sourcing as an HA policy. For low latency applications, avoiding creation of garbage or object allocation is desirable because that will result in GC pauses that cause latency spikes. In some applications, even a minor gc pause that results from promoting newly allocated objects to the tenured generation would violate SLAs. |
This section discusses the techniques application developers can apply to ensure that application code is garbage free, as well as some of the costs and alternatives application developers should consider before choosing to exploit them. |
For the JVM to avoid any GC pauses, it isn't sufficient for the platform alone to produce no garbage; the application business logic must also not produce garbage. Talon provides tools to help applications achieve this. For an application to achieve zero garbage, it must:
...
The following sections describe the various techniques that can be used by application to interoperate with the platform in a zero garbage fashion.
| Children Displaypagetree |
|---|
| depthroot | 1 |
|---|
| @self | excerpt | true |
|---|
|
