Hi, recently I was trying the Flexmonster Dataserver on our ECS Server with Windows OS, but notice some issue as below:
I would like to propose to have few APIs for below:
attached is the log file for your reference
Thank you for posting your question.
Regarding your suggestions for the API, please find our answers below:
Speaking of memory issues you’ve mentioned, please see our response in the related thread.
Please let us if we’ve managed to answer your questions in full or if there is still anything we can help you with.
Thanks for the prompt reply. I am looking forward to having the option to reload the data through the client-side request. Which is more applicable to us, as AWS EC2 we subscribed has limited CPU and Memory, which also shared among many of our projects and application. Refresh data by time will consume too many resources if too frequently, but less frequency will also cause the report pulled can not reflect the latest.
Please also help to implement GC properly, try to release the memory ASAP once the request fulfilled. We may want to have few indexes in Flexmonster DataServer for large data reports, we do not need it to cache the report data in memory, this is because AWS EC2 and RDS in the internal network with large bandwidth, and thanks to Flexmonster Pivot we no need the execute complex store procedure at RDS to group the data, so it is very fast for Flexmonster DataServer to retrieve the data from RDS(no need to preload or cache data).
Thank you for providing further details on your use case.
We also wanted to clarify a couple of things about how the Data Server works. More specifically, once started, the data sets for each of the indexes specified in the configurations are loaded to the memory – this is necessary for the Data Server to be able to build the query structure based on the corresponding data set.
Speaking of the
CacheSizeLimit Data Server configuration, it defines how many responses are cached for every index – when set to 0, the caching is disabled and the responses will not be saved.
We hope we’ve managed to explain the above specificities of Flexmonster Data Server clearly – please let us know if there are still any questions on this that we can help you with.