Skip to content
This repository has been archived by the owner on Jul 14, 2024. It is now read-only.

Keep an eye on indexes size (geo:Area_0, org:Organization_0, geoname...) #156

Open
mdutoo opened this issue Jan 19, 2016 · 1 comment
Open

Comments

@mdutoo
Copy link
Collaborator

mdutoo commented Jan 19, 2016

Here are the biggest collections'index size:

rs0:SECONDARY> db["geoname_0.geoname:GeoDB_0"].totalIndexSize()
166258960
rs0:SECONDARY> db["geo_1.geo:Area_0"].totalIndexSize()
127480192
rs0:SECONDARY> db["org_1.org:Organization_0"].totalIndexSize()
21878976
rs0:SECONDARY> db["oasis.meta.dcmi:mixin_0"].totalIndexSize()
171696

Right now, it's OK: even geoname and geo, though mostly cold, static data, are an order of magnitude smaller (120-170MB) that the portal's geo replication data.

However, it's the different kinds of data that end up making up a big total in the Datacore. So we should keep an eye on it in the future (and on esp. Portal but also Kernel indexes, but also Datacore & Portal java processes which it has to share RAM with), in case it becomes a performance problem.

@OzBruno
Copy link

OzBruno commented Jan 19, 2016

Don't forget that I will upload around 15 other countries in geoname including the biggest : United States and China.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants