[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 19:55:01 -0400
- In-reply-to: <CAMhuimjRnRnZruc1xVCuC0q+_MKJSeaT8AGnH-9sndsyCb=iTg@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> <25853.1563297804@turing-police> <CAMhuimjRnRnZruc1xVCuC0q+_MKJSeaT8AGnH-9sndsyCb=iTg@mail.gmail.com>
On Tue, 16 Jul 2019 15:54:10 -0600, Ken Gilmour said:
> We have a different use case to traditional analytics - We're aimed at
> consumers and small businesses, so instead of a SOC with one big screen
> refreshing 10000 rows of only alert data every 30 seconds, we have
> thousands of individuals refreshing all of their data every 30 seconds
> because there are comparatively less alerts for individuals than
> enterprises.
Plenty of room for lots of optimizations there, especially in conjunction
with some client-side caching. If they're generating enough *new* events
every 30 seconds to cause any significant load, they're either in the middle
of a major event (something that shouldn't happen too often) or they have
the logging is set to be so verbose that they're likely to miss actual important
messages.
-------------- 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/23288b39/attachment-0001.sig>