Hi,
Thanks for the replies.
It's a 2.2 kB configuration file. And it will not grow by the time.
So caching in memory will not be a big issue.
Found that it can be stored in application context.
Jaggery documentation says,
1. %
2. //Putting a property to the application context
3.
Hi,
If the file content is stored in memory, memory consumption would grow if
it reads a big file or several files. How about using a cache of a fix
size?
What kind of files it would read multiple times, if they are configuration
files only the important data could be stored in the memory.
Could
Hi,
What about population your file data to temp db and access it and
update/delete when needed?
Thanks
On Thu, Aug 21, 2014 at 1:23 AM, Udara Liyanage ud...@wso2.com wrote:
Hi,
If the file content is stored in memory, memory consumption would grow if
it reads a big file or several
Hi,
i want to optimize file read in jaggery application, which reads same file
several times.
However it is not recommended to store the content in the session.
Muduranga suggested that to store it in Application context.
Any suggestions would be appreciated.
Thanks Regards,
Ishara Cooray
