[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Colo in Africa
- Subject: Colo in Africa
- From: valdis.kletnieks at vt.edu (Valdis Klētnieks)
- Date: Tue, 16 Jul 2019 13:23:24 -0400
- In-reply-to: <CAMhuimhEqzhR-b-56frE=UJpPabAexOZb8YivF9__CRyd765rg@mail.gmail.com>
- References: <CAMhuimgGz+hRf4zQpwEb3o+3-hih75=zXdDgv5dU6cdVZ4-5fA@mail.gmail.com> <CADrHqgyk3akd0vai3W3VWS3zPn7wp=Qr0vM9MtmcqfWuDh97YA@mail.gmail.com> <CAMhuimh7LZLpzoL8Js7wzHhxzgPr3thXjMOCZoBg6KXEJ2RodA@mail.gmail.com> <CADrHqgxWETbE6UY+AOFK-eKZOcs=Raz71_YbYYjq8ydc7twwrA@mail.gmail.com> <CAMhuimhEqzhR-b-56frE=UJpPabAexOZb8YivF9__CRyd765rg@mail.gmail.com>
On Tue, 16 Jul 2019 10:39:59 -0600, Ken Gilmour said:
> These are actual real problems we face. thousands of customers load and
> reload TBs of data every few seconds on their dashboards.
If they're reloading TBs of data every few seconds, you really should have been
doing summaries during data ingestion and only reloading the summaries.
(Overlooking the fact that for dashboards, refreshing every few seconds is
usually pointless because you end up looking at short-term statistical spikes
rather than anything that you can react to at human speeds. If you *care* in
real time that the number of probes on a port spiked to 457% of average for 2
seconds you need to be doing automated responses....
Custom queries are more painful - but those don't happen "every few seconds".
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 832 bytes
Desc: not available
URL: <http://mailman.nanog.org/pipermail/nanog/attachments/20190716/91fb9f90/attachment.sig>