NOSTR and performence
Do using NOSTR in a large scale affect performance?
I remember DCoder said it is only for testing.
I however always uses it(to lazy to use the csf).
Question information
- Language:
- English Edit question
- Status:
- Solved
- For:
- Ares Edit question
- Assignee:
- No assignee Edit question
- Solved by:
- YR M0ddEr
- Solved:
- 2012-05-01
- Last query:
- 2012-05-01
- Last reply:
This question was reopened
| AlexB (alexander-b) said : | #1 |
That's timing. Just two days ago I added a caching system for NOSTR and MISSING: texts. (Not available yet)
Texts are re-read for every occurrence in an INI file (multiple times because each file can re-parse them). This happens for each match loaded. My tests weren't exactly scientific, but it showed unit and super weapon names will not be re-added every frame. So a bunch of NOSTR: doublettes should not significantly add to the 5000+ strings in YR. Used on large scale or after many many matches in a row it might.
| YR M0ddEr (yr-m0dder) said : | #2 |
Thanks and nice work on the cache.
| YR M0ddEr (yr-m0dder) said : | #3 |
Is this feature available in 0.2 Rc1?
| AlexB (alexander-b) said : | #4 |
No, I rather consider it a new feature. At least it's no bugfix. It will most likely get into 0.3.
