Hi Randy,
rbaker wrote: > Any ideas on why we are seeing such a difference in behaviour? As I recall you were exporting to the database; is that still true? If so, what does the server's disk I/O load look like? When database export is enabled, IM (the server itself, not the database) writes much more to disk than normal, as it stages data for export. Because there are significant differences in the way IM interacts with the disk on Windows versus Linux, it's possible that polling on your new server is stalling while waiting on disk I/O. That typically manifests as short-term packet loss, since IM isn't counting responses that it perceives as 'too late'. We have a special built-in probe used to debug such problems; you can find it under Experimental -> InterMapper. Create a device with that probe, and let it run for a while. Then take a look at the status window and please send the results in an email to support. We'll use the resulting support ticket to respond to you once we've taken a look at the data. A note for others reading this: do not use the InterMapper probe pre-emptively as a diagnostic tool. It's marked 'Experimental' for a reason, and is designed exclusively for debugging specific problems. It doesn't produce meaningful results on a normal IM server. ----------- David Schnur Dartware, LLC -------------------- m2f -------------------- Read this topic online here: http://forums.intermapper.com/viewtopic.php?p=3975#3975 ____________________________________________________________________ List archives: http://www.mail-archive.com/intermapper-talk%40list.dartware.com/ To unsubscribe: send email to: [email protected]
