|
95 | 95 |
|
96 | 96 | **Behaviors Under Large Transaction** |
97 | 97 |
|
98 | | -1. no infinispan setting + low JVM heap (synchdb.jvm_max_heap_size=128) |
| 98 | +no infinispan setting + low JVM heap (synchdb.jvm_max_heap_size=128) |
99 | 99 |
|
100 | | ---> OutOfMemory error will occur |
| 100 | +* --> OutOfMemory error will occur |
101 | 101 |
|
102 | | -2. low JVM heap (128) + high infinispan off heap (2048) |
| 102 | +low JVM heap (128) + high infinispan off heap (2048) |
103 | 103 |
|
104 | | ---> large transaction handled successfully |
| 104 | +* --> large transaction handled successfully |
105 | 105 |
|
106 | | -3. low JVM heap (128) + low infinispan off heap (128) |
| 106 | +low JVM heap (128) + low infinispan off heap (128) |
107 | 107 |
|
108 | | ---> passivation will occur |
109 | | ---> `ispn_[connector name]_[destination database name]` size will grow during processing and reduce once large transaction finished processing |
110 | | ---> large transaction handled successfully but at slower speed. |
| 108 | +* --> passivation will occur |
| 109 | +* --> `ispn_[connector name]_[destination database name]` size will grow during processing and reduce once large transaction finished processing |
| 110 | +* --> large transaction handled successfully but at slower speed. |
111 | 111 |
|
112 | | -4. low JVM heap (128) + high infinispan heap (2048) |
| 112 | +low JVM heap (128) + high infinispan heap (2048) |
113 | 113 |
|
114 | | ---> OutOfMemory error will occur |
115 | | ---> do not configure infinispan to use more heap memory than JVM max heap. |
| 114 | +* --> OutOfMemory error will occur |
| 115 | +* --> do not configure infinispan to use more heap memory than JVM max heap. |
116 | 116 |
|
117 | | -5. low JVM heap (128) + low infinispan heap (64) |
| 117 | +low JVM heap (128) + low infinispan heap (64) |
118 | 118 |
|
119 | | ---> passivation will occur |
120 | | ---> `ispn_[connector name]_[destination database name]` size will grow during processing and reduce once large transaction finished processing |
121 | | ---> not recommended as half of the JVM heap can potentially be used by infinispan and may not have enough left for other Debezium operations |
| 119 | +* --> passivation will occur |
| 120 | +* --> `ispn_[connector name]_[destination database name]` size will grow during processing and reduce once large transaction finished processing |
| 121 | +* --> not recommended as half of the JVM heap can potentially be used by infinispan and may not have enough left for other Debezium operations |
122 | 122 |
|
123 | | -6. low JVM heap (128) + same infinispan heap (128) |
| 123 | +low JVM heap (128) + same infinispan heap (128) |
124 | 124 |
|
125 | | ---> not recommended as all of the JVM heap can potentially be used by infinispan and eventually causing OutOfMemory error |
| 125 | +* --> not recommended as all of the JVM heap can potentially be used by infinispan and eventually causing OutOfMemory error |
126 | 126 |
|
127 | | -7. high JVM heap (2048) + low infinispan heap (128) |
| 127 | +high JVM heap (2048) + low infinispan heap (128) |
128 | 128 |
|
129 | | ---> passivation will occur |
130 | | ---> `ispn_[connector name]_[destination database name]` size will grow during processing and reduce once large transaction finished processing |
131 | | ---> large transaction handled successfully |
132 | | ---> not efficient - as only a small portion of JVM heap is used as cache + unnessary passivation. |
| 129 | +* --> passivation will occur |
| 130 | +* --> `ispn_[connector name]_[destination database name]` size will grow during processing and reduce once large transaction finished processing |
| 131 | +* --> large transaction handled successfully |
| 132 | +* --> not efficient - as only a small portion of JVM heap is used as cache + unnessary passivation. |
0 commit comments