unicode-org
jsp: half of the build time is cache files
1⁄2 of the time is spent in Regenerate the property cache files
@eggrobin can this be cached safely?
This is tricky. Unless the code changes, the old versions are stable (but not the dev version). But then if the code changes, all bets are off.
ok, so it could skip the dev version, and then hash on all of the code. Maybe not worth it.
The caching isn't even working, because in the JSP's console I see
2025-01-28 18:12:55.145:INFO:oejs.session:main: DefaultSessionIdManager workerName=node0
2025-01-28 18:12:55.146:INFO:oejs.session:main: No SessionScavenger set, using defaults
2025-01-28 18:12:55.146:INFO:oejs.session:main: node0 Scavenging every 660000ms
Loading back to 17.0.0.0...
Loading UCD 16.0...
Loaded non-Unihan properties for 16.0 (4303 ms)
Loaded Unihan for 16.0 (3420 ms)
Loaded UCD 16.0 in 7732 ms
Loading UCD 17.0...
Loaded non-Unihan properties for 17.0 (3423 ms)
Loaded Unihan for 17.0 (546 ms)
Loaded UCD 17.0 in 3969 ms
Loaded UCD history back to 17.0.0.0 in 11 s
2025-01-28 18:13:07.380:INFO:oejsh.ContextHandler:main: Started o.e.j.w.WebAppContext@3e27aa33{UnicodeJsps,/UnicodeJsps,file:///tmp/jetty-0_0_0_0-8080-UnicodeJsps_war-_UnicodeJsps-any-9983956548832997525/webapp/,AVAILABLE}{/var/lib/jetty/webapps/UnicodeJsps.war}
Loading back to the dawn of time...
Loading UCD 16.0...
Loaded non-Unihan properties for 16.0 (1 ms)
Loaded Unihan for 16.0 (0 ms)
Loaded UCD 16.0 in 1 ms
Loading UCD 17.0...
Loaded non-Unihan properties for 17.0 (1 ms)
Loaded Unihan for 17.0 (0 ms)
Loaded UCD 17.0 in 1 ms
Loading UCD 15.1...
that might be causing some runtime issues!
That is the time spent loading the cache.
Generating the cache from the data files is more like 20 s for each version of Unicode.