On Wed, 2006-08-16 at 07:21 +0200, Michel Stam wrote:
> I'm still thinking of ways to improve the code (which is basically also
> limited by the time I can spend on it).
> Something thats been on my mind is improving speed by having one or two
> threads retrieve the data for the tables into memory periodically, so
> SNMP queries can be served instantly. This should also significantly
> reduce the number of times MySQL is bothered by the agent.
> I'll have to look into the threading as MySQL provides it, I saw MySQL
> has a few wrapper functions for it.
for the ndb status information you could keep a cached copy and only
update when you get an event (using the mgm events mechanism for node
start/stop events).
ndb_mgm doesn't currently do it this way.
a recent change i made is that when you call ndb_mgm_get_status (IIRC
that's what it's called) it forces a heartbeat between the DB nodes so
that the status is always up to date (unless the heartbeat takes too
long, then it could be out of date... but you're probably going to have
nodes being kicked out of the cluster by then).
--
Stewart Smith, Software Engineer
MySQL AB, www.mysql.com
Office: +14082136540 Ext: 6616
VoIP: 6616@stripped
Mobile: +61 4 3 8844 332
Jumpstart your cluster:
http://www.mysql.com/consulting/packaged/cluster.html
Attachment: [application/pgp-signature] This is a digitally signed message part signature.asc
Attachment: [application/pgp-signature] This is a digitally signed message part signature.asc
