Hi Debbie,
> I'm not sure how to get Intermapper server to tell me about interfaces and > datasets. The best way is through the database's Overview page; if you open a browser on the IMDC machine, you can point it at https://localhost:8182/~imdatabase/index.html. The charts on that page show you how many devices, interfaces, dataset, datapoints, etc. are present in your database. > When I try and get IMDC reports to "check all" everything to tell me, Safari > starts to warn me about slow scripts and it takes a long time to see anything. Sorry about that; it's a known problem that affects larger servers. In 5.5 we've optimized several of those operations, so they run faster and also give control back to the browser periodically, to prevent it from showing the warning. > I just tried it in FireFox 3.6.19 instead, and it doesn't draw the screens > right in the popup windows, so the "check all" and "uncheck all" overlap the > device list and are tricky to select (Mac OS 10.6.8). That sounds like a bug; I've created a support ticket and will follow up shortly. > we're thinking about asking the system people for a second core on the VM, > but if it shouldn't do this, that would be interesting to know. The database can take advantage of 2-3 cores, but in your case the activity is all in one place, so the benefit would be small. You're also not running IM on the same machine; if you were, a second core would matter. Reports, however, can each use their own core, using up to about eight if you ran that many at a time. So I wouldn't worry about adding another core until you start running more reports. It won't have a significant effect on import speed. > the policy on the IMDC side is: > > original data 2 weeks > 5-minute samples 1 month > Hourly samples 2 years > daily samples forever > That's a good policy; I wouldn't change it, even after you're done collecting old data. Your settings for Original and 5-Minute data, which make up most of the database's size, are already quite reasonable. So I'm not immediately seeing reason for the slow imports. The three main factors in import speed are number of datasets, retention policy, and disk access. Your policy is fine. You seem to have a lot of datasets, but so far it doesn't look like enough to slow things down this much. If there's a lot of activity on your SAN, that could make a big difference, but that's harder to quantify. Since we're getting a little specific here, I'll create a support ticket for this, so we can continue with this off-forum. You'll get an update on that shortly. Also, while looking at the IMDC auto-reports today, I noticed a duplicate-datasample error from your IMDC, labeled as 5.4.4. So it looks like you upgraded, though that error might just be a left-over from the previous version. If I see another such report, then your duplicate datasample situation was evidently not part of the set that we fixed. If that's the case, I'll create a support ticket so we can keep you updated as we fix it. David -------------------- m2f -------------------- Read this topic online here: http://forums.dartware.com/viewtopic.php?p=3554#3554 ____________________________________________________________________ List archives: http://www.mail-archive.com/intermapper-talk%40list.dartware.com/ To unsubscribe: send email to: [email protected]
