Welcome Guest, Not a member yet? Register   Sign In
[Best practice] Heavy background tasks?
#5

[eluser]jedd[/eluser]
This is a hugely broad question.

The general response is to have a separate OLAP database for this kind of work. If your report cycle is 24 minutes, then this is less (but still) feasible -- you'd just have to be more careful in your assessment of whether it's worth the cost of maintaining a separate and unique schema dedicated to the reporting side of the system.

Have you done any performance tests already to determine if what you want to do does or does not work properly on the extant hardware and database? I'd assume you have, if you're looking at ways to reduce that load.

If it's marginal, just throw more CPU and memory at the problem.

Tune the crikey out of your database.

Depending where you are in the development cycle, the option of de-normalising your primary database may exist.

As I say .. huge question, with way too many variables.


Messages In This Thread
[Best practice] Heavy background tasks? - by El Forum - 04-06-2009, 10:11 PM
[Best practice] Heavy background tasks? - by El Forum - 04-06-2009, 11:49 PM
[Best practice] Heavy background tasks? - by El Forum - 04-06-2009, 11:54 PM
[Best practice] Heavy background tasks? - by El Forum - 04-07-2009, 12:03 AM
[Best practice] Heavy background tasks? - by El Forum - 04-07-2009, 04:46 AM
[Best practice] Heavy background tasks? - by El Forum - 04-07-2009, 05:01 AM
[Best practice] Heavy background tasks? - by El Forum - 04-07-2009, 05:18 AM



Theme © iAndrew 2016 - Forum software by © MyBB