Hi Mark! Well that's really the million dollar question isn't it? =P
The honest answer to that question is that our product grew insanely fast and aren't correctly archiving our data out of these high traffic / high volume tables. We shouldn't have to be doing high traffic reads out of tables with fifty to a hundred million records. Doing dirty reads should never HAVE to be an absolute necessity, it's just really useful under certain circumstances (which is obviously a debatable point). That being said, it's unfortunately the situation that I find myself in until i can remedy all of the issues in the existing system. I have been making a conscious effort (and great strides) to relieve the pressure on these tables by archiving and allowing historical access via views, however it's difficult to tackle the monster as a whole and still move forward (especially in a fast paced environment). Out of curiosity, does Transfer do any kind of caching on objects even if caching is turned off for an entity in the config (and global caching is off)? I know certain frameworks use multiple layers of caching, so I'm just curious. BTW, I apologize for my frequent typos. I'm a lousy proof-reader. Thanks again for your feedback and time! Nick --~--~---------~--~----~------------~-------~--~----~ Before posting questions to the group please read: http://groups.google.com/group/transfer-dev/web/how-to-ask-support-questions-on-transfer You received this message because you are subscribed to the Google Groups "transfer-dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/transfer-dev?hl=en -~----------~----~----~----~------~----~------~--~---
