Hello. Where should i patch in v.3.3.2's import_runtime.( maybe https://secure.opsera.com/wsvn/wsvn/opsview/trunk/opsview-core/bin/import_runtime?rev=3336&peg=3336) I look into the script but patched parts( https://secure.opsera.com/wsvn/wsvn/opsview/trunk/opsview-core/bin/import_runtime?op=diff&;) are no diffrent.
and where service_saved_state table is used? I can't find the table in odw DB schema diagram. 2010/1/19 Ton Voon <[email protected]> > > On 19 Jan 2010, at 02:33, Kang wrote: > > https://secure.opsera.com/jira/browse/OPS-950 > > I'm using Opsview v 3.3.2 now. > but i think there is no service_saved_state table(in our DB, its size is > 220MB) growing problem. > ( i executed the DELETE query which you pasted but there is no change in > table data length size. ) > i doubt it is the main cause of performance degradation. > > > On one customer's large system, this was a problem which we saw during the > data load, so we've fixed this problem and raised it on the mailing lists. > > Your system may have a different issue. We I can't look it without a > support contract :( > > The DELETE will not change the table data length based on the length of the > data file - you will need to run a mysql optimise to do that. > > You can see the dataload timings by running this command: > http://docs.opsview.org/doku.php?id=opsview-community:odw#how_long_does_a_dataload_take > > Ton > > > _______________________________________________ > Opsview-users mailing list > [email protected] > http://lists.opsview.org/lists/listinfo/opsview-users > >
_______________________________________________ Opsview-users mailing list [email protected] http://lists.opsview.org/lists/listinfo/opsview-users
