Hi Grant,

You are using the In-Memory DB correctly.

You should be able to cache any of the views you are using,
and not be receiving the 'An error has occurred' message.

Could you please email the revelant 'Yellowfin.log' file to support.

Also which build were you using?

Thanks,
David

Hi David,

In-Memory DB uses real memory
I suppose I thought In-Memory was just a fancy word
For disk caching or something

It uses real memory and / or memory swap space
All of my sites are on Linux machines
And run on the same box as their ERP system

Memory of course is required for the ERP users / other tasks etc

So when I get this all working
Data In-Memory will be fast which will be good
But
Do you have any advice / experience
Re what happens when YellowFin In-Memory
Grabs a fair chunk of memory etc

Thanks - Grant

Hi Grant,

Yes, it does use actual memory, though rest assured the in-memory database is cleared after each Tomcat reboot. It will use the allocated amount of memory previously set for the Java (so this can always be changed).

Though in terms of the dashboard taking up to 40secs when first logging in, this cannot be changed at the moment.
As this dashboard will cache all the data only after being opened.

So if your caching is to refresh every day, then every day the dashboard will need to be reloaded into cache.

We are thinking of ways to automatically cache these dashboards, though I believe this will take some time, as this would be a major change.


Regards,
David

Hi David,

Your comments
"We are thinking of ways to automatically cache these dashboards, though I believe this will take some time, as this would be a major change."

Keep thinking and harder if possible
Most of my DashBoards take 30-60 Seconds
After Caching each less then 10 Seconds
Let me know if anything is happening with this
Be great if you could do something in this area


Also noting your comments re my in-memory DB problem.
This was not working / failing bacause

Your Comments
We have confirmed this is due to the ?TIME? MySQL data type and have raise it as a bug (TASK ID = 103827).
We will have to make some changes to the in-memory DB to allow it to handle such data types.
This will be implemented in a future build, and you will be notified when this happens.


Thanks - Grant

Hi David,


Your Comments
We have confirmed this is due to the ?TIME? MySQL data type and have raise it as a bug (TASK ID = 103827).
We will have to make some changes to the in-memory DB to allow it to handle such data types.
This will be implemented in a future build, and you will be notified when this happens.

Has this been resolved as yet ?

Thanks - Grant

Hi Grant,

Apologies for the delayed response.

This issue hasn't been fixed as yet, though as a workaround you could cache the view into a blank MySQL database as this should work.

Just note because cached views do not support joins you could end up with a fairly large database.

Regards,
David