eggplant_casserole
Member
I'm an admin on a Xenforo forum. We're preparing to move to a new server and are considering purchasing Enhanced Search.
The server specs are as follows:
I hadn't checked the usage stats before, but I looked after installing the above and they'd gone to 2.7 Gb used. Seemed excessive for a server running nothing! So I checked and Elasticsearch was the guilty party.
It's been a couple of days and I've been busy. So I check again. Nothing has changed, but now Plesk reports:
There's nothing on the server other than a test HTML file I downloaded to check the compression was working.
I checked with vmstat -s and the result was a little different:
Is that only counting physical RAM used?
So I tried top. Elasticsearch would come and go every 5 seconds or so, but it reported 29.9% RAM usage. So it still seems to be using 2 Gb or more doing nothing!
I've not used Elasticsearch before - I'm only doing so because users are complaining about poor search results and not being able to search for 3 letter words (there are many used in our topic area).
There's not much info on the buy page regarding requirements - it says you need Java and Elasticsearch and it's probably only suited for a dedicated server. We are running a dedicated server. However, most stuff I've seen online about configuring Elasticsearch talks about using server clusters, or at least a dedicated server JUST for Elasticsearch! We can't really afford to do that.
So....
Is the RAM usage going to jump drastically when we have copied a Xenforo forum across with over 850,000 messages and nearly 25,000 users? Is the server going to be adequate for our needs? What can we do to stop Elasticsearch hogging RAM... and is it a good idea?
The server specs are as follows:
- Intel Xeon E3-1231 v3 @ 3.40 GHz
- 8 Gb RAM
- 256 Gb SSD
- CentOS 7
- Plesk Onyx 17
I hadn't checked the usage stats before, but I looked after installing the above and they'd gone to 2.7 Gb used. Seemed excessive for a server running nothing! So I checked and Elasticsearch was the guilty party.
It's been a couple of days and I've been busy. So I check again. Nothing has changed, but now Plesk reports:
Total 7.6 Gb Used 6.25 Gb Free 1.35 Gb Shared 0 B Buffer 254.94 Mb Cached 2.57 Gb Usage 48.42%
There's nothing on the server other than a test HTML file I downloaded to check the compression was working.
I checked with vmstat -s and the result was a little different:
7969744 K total memory
2987892 K used memory
3972704 K active memory
1855860 K inactive memory
1396312 K free memory
261056 K buffer memory
3324484 K swap cache
8388604 K total swap
0 K used swap
8388604 K free swap
Is that only counting physical RAM used?
So I tried top. Elasticsearch would come and go every 5 seconds or so, but it reported 29.9% RAM usage. So it still seems to be using 2 Gb or more doing nothing!
I've not used Elasticsearch before - I'm only doing so because users are complaining about poor search results and not being able to search for 3 letter words (there are many used in our topic area).
There's not much info on the buy page regarding requirements - it says you need Java and Elasticsearch and it's probably only suited for a dedicated server. We are running a dedicated server. However, most stuff I've seen online about configuring Elasticsearch talks about using server clusters, or at least a dedicated server JUST for Elasticsearch! We can't really afford to do that.
So....
Is the RAM usage going to jump drastically when we have copied a Xenforo forum across with over 850,000 messages and nearly 25,000 users? Is the server going to be adequate for our needs? What can we do to stop Elasticsearch hogging RAM... and is it a good idea?