• Cashing or DB hit for faster speed?

    MarkGrillo Member March 16, 2016 at 12:13 pm

    I have a db with 3 tables, each table has about 150,000 records, linked to each other by ID, 2 to 4 columns per table.
    The tables might change once every 3 or 4 months.
    If i take a backup of the data it totals up to 12MB.

    I have a Java back end and am using Hibernate right now to connect and get data out of the tables.
    I was wondering if it would be better to cache the data and keep it in memory for faster speeds.

    #9577
  • Ganesh Member March 16, 2016 at 12:13 pm

    The tables are small both in record count and size.

    Caching would really not offer much improvement, so to avoid the hassle of clearing the cache (and remembering to do so) when you do make a change to the db, I wouldn’t bother caching.

    #9578
  • Amit Member March 16, 2016 at 12:14 pm

    Go with hibernate and leave the application as it is

    #9579
Viewing 2 reply threads
  • You must be logged in to reply to this topic.
en_USEnglish
en_USEnglish