Hi Kevin, Yesterday kevin brintnall wrote:
> This patch introduces a new way to feed updates to 'rrdcached'. This > feature is designed for sites with an *EXTREMELY* high update rate. yes speed, speed, speed. > A client on a high-privilge control socket may issue the following > command: > > -> SLURP /somewhere/filename > <- 0 Processed 6840502 lines, 6840502 entries, 0 failures iiks ... being able to instruct 'network services' to read in data from a local file system always sends shivers down my spine. I would much rather see an extension to the UPDATE command where I could tell it how may lines I am going to submit. And then proceede to send the data. This should be similarly fast I guess but the accessing of the filesystem would be a client responsability. otoh, what would happen if the normal protocol was enhanced, so that the client could submit an id with its update command. The server would then tag its responses with these ids. The client would then not have to wait for each response, but could match them 'later'. cheers tobi -- Tobi Oetiker, OETIKER+PARTNER AG, Aarweg 15 CH-4600 Olten, Switzerland http://it.oetiker.ch [EMAIL PROTECTED] ++41 62 775 9902 / sb: -9900 _______________________________________________ rrd-developers mailing list [email protected] https://lists.oetiker.ch/cgi-bin/listinfo/rrd-developers
