Book a Demo

Author Topic: Cache does not work  (Read 6158 times)

thomas.kilian

  • Guest
Cache does not work
« on: March 26, 2008, 03:44:46 am »
I made some performance measurements. According to that, the so-called cache inside EA (Repository.EnableCache) does not work. If turned on it accounts (very best case) for 5% speed improvement. I use automation a lot for querying the DB to make all kinds of exports/reports. Here I strongly count on a non-changing database - and a working cache. EA actually passes everything to the SQL server. If you have a big one sitting behind you it might cache for you, but I work locally on my machine. Now I have wrapped all Repository calls with a cache and it boosts with a factor of 10 (which is 90% instead of 5%)! So what is that EA cache worth at all? >:(

«Midnight»

  • EA Guru
  • *****
  • Posts: 5651
  • Karma: +0/-0
  • That nice Mister Grey
    • View Profile
Re: Cache does not work
« Reply #1 on: March 26, 2008, 09:59:51 am »
I'm not quite getting what you mean by "wrapped all Repository calls with a cache..."
No, you can't have it!

thomas.kilian

  • Guest
Re: Cache does not work
« Reply #2 on: March 26, 2008, 08:22:24 pm »
I use a proxy class to catch all Repository methods (esp. the getbyid and guid). I can then use my own cache mechanism instead of the not existing EA cache.

«Midnight»

  • EA Guru
  • *****
  • Posts: 5651
  • Karma: +0/-0
  • That nice Mister Grey
    • View Profile
Re: Cache does not work
« Reply #3 on: March 26, 2008, 09:56:59 pm »
That's what I was afraid of. I've been hoping to avoid the overhead, but I suspect that my future leads that way.

Of course that opens up some other avenues, but we can discuss that elsewhere.
No, you can't have it!