Rev 1373 | Show entire file | Regard whitespace | Details | Blame | Last modification | View Log | RSS feed
| Rev 1373 | Rev 1461 | ||
|---|---|---|---|
| Line 327... | Line 327... | ||
| 327 | 327 | ||
| 328 | ### OBJECT_CACHING |
328 | ### OBJECT_CACHING |
| 329 | 329 | ||
| 330 | OIDplus::baseConfig()->setValue('OBJECT_CACHING', true); |
330 | OIDplus::baseConfig()->setValue('OBJECT_CACHING', true); |
| 331 | 331 | ||
| 332 | Object caching reads all objects in the memory. This increases performance |
332 | Object caching reads all objects from the database in the memory at every request. |
| - | 333 | This increases the speed on small databases (but also uses more memory), |
|
| - | 334 | but makes OIDplus VERY slow if the database is big (> 10.000 OIDs). |
|
| - | 335 | ||
| 333 | performance but also increases memory usage on large databases. |
336 | So, if you want (or must) use little RAM, or have a lot of objects in the |
| - | 337 | database, please turn off `OBJECT_CACHING`. |
|
| 334 | 338 | ||
| 335 | ### FORCE_DBMS_SLANG |
339 | ### FORCE_DBMS_SLANG |
| 336 | 340 | ||
| 337 | OIDplus::baseConfig()->setValue('FORCE_DBMS_SLANG', ''); |
341 | OIDplus::baseConfig()->setValue('FORCE_DBMS_SLANG', ''); |
| 338 | 342 | ||