Hi Elizabeth,
Thank you for replying.
On 22/7/2015 3:33 AM, Elizabeth McGurty wrote:
First I would work to learn patterns in time increments, which occur
most often, and plan from there.
We do know that - we have a few peak hours when more data comes in, and
then there are hours (like night time) where the data drops to a trickle
for some of the records. However, there are some status emails, etc.
that come at a fixed frequency - few times an hour, irrespective of the
hour.
Then I would design with regard to DB code and servers, optimal
Master-slave replication. Pretty sure that in replication WHERE
clauses like (where recorded_on >= (now() - '24 hr'::INTERVAL) could
be eliminated at the user level. But I am not certain.
While this is something that might help, I'm more looking at solutions
that involve having hot data tables in the manner:
> All the data
> Data for the last 24 hours
> Data for the last 2 hours
That way, when we want something recent, we would just query the most
recent table, but in the few occasions that we need something more, we
go to the larger tables that are sharded.
Best Regards,
Mohit.
--
You received this message because you are subscribed to the Google Groups "Ruby on
Rails: Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to rubyonrails-talk+unsubscr...@googlegroups.com.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/rubyonrails-talk/55AF9897.3000403%40onghu.com.
For more options, visit https://groups.google.com/d/optout.
