Hello Andrea,
Indeed I missed this while searching for past discussions about jdbc
performance. In the meantime I read your proposal, the email discussion,
and had a look at the PR. That looks like great stuff. But it is not
entirely clear to me what effect your changes have on the amount of name
queries per request with jdbcconfig, are they significantly reduced?
Perhaps my suggestion can still make a difference.
On 15-06-17 16:02, Andrea Aime wrote:
Nowadays there is from a cache keyed by immutables (ids), you are
adding a cache of mutables (I believe you need to cache by qualitified
name, ws: name), so how are you going to spread the word across
cluster nodes when a layer or workspace name changes, or gets removed?
Is the hz-cluster covering this already?
yes, hz-cluster already covers a joint cache. Upon a change, the item
would be invalidated based on the old name and recached with the new name.
Regards
Niels
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Geoserver-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
