ORIGINAL: michaelm
ORIGINAL: beppi
Some technical question.
It seems that you are using some sort of internal database library to store the tracker data.
What i saw now, cause i have some performance problems (have a very large database with lot of turns) that whenever i launch the tracker that the system resources for my local wlan (Intel driver) skyrocket to almost 50% too. Is it possible that with your connection to the database you are using the external IP adress and not the internal loopback so all traffice regarding to loading the tracker are looped over the external network connection and not the internal loopback ?
I haven't tracked it in detail but it seems a little bit strange (and could be responsible for some of the performance problem during loading).
WLKEEPER.exe is the Intel drivers of the WLAN.
I assume the HD with the tracker database is local to your PC and not on LAN-connected HD.
It is not uncommon that today you do a abstraction on the TCP Layer 7 and no longer care for System/Lan/Wan or anything else. You usually do not even care about any protocols as the libraries in combination with the operating system handle whatever you need.
From a quick look it seems that org.hsqldb.jdbcDriver works exactly that way and does not distinguish between System and Lan and Wan and anything else as a local connection would just be a local connection on the loop back.
And as i know from experience (saw that problems more than once in software or system configuration) for example if you access your localhost (127.0.0.1) not by that IP(or by localhost as name) instead by your external IP that all traffic is looped over the NIC (at least the driver if it is good developed, but even saw once communication to the next switch and back to the NIC, if you use more than one IP Adress). And don't think that any data is sent to the LAN instead it seems that for an unknown reason during loading of the tracker the driver of the NIC uses and unusual high amount of system resources.
Saw that problem once in an ESX Environment when everyone was complaining of the bad performance between the different VMS, and instead of the local connection between the VMS the external IPS where accessed which resulted in a heavy load on the NIC.
It was just an idea when i saw that problem today and could be a bad configured notebook (Company one) or some other driver which forces all local connections over the NIC (Anti Virus stuff or security stuff or VPN Stuff or whatever [;)]). Will track it a little bit further if i have time and as i said was just a question.