Profiler question

[dirt]

I have been using and running NWNX for a few years now. Recently, we just moved our NWN PW to a new dual-core AMD server.

The first time we fired it up on the box, we had some weird things happen(AT's not working, NPC conversations not fire, no spawns ,etc).

Since that time, occasionally we get periods where it almost seems like the box is running to fast(spells animations off, creatures flying across the screen, and some DB issues).

Now to the question, when I looked at the profiler log I saw a bunch of negative script call times....for example:

nw_c2_default9............-40msec..............34523 calls

Has anyone ever seen this before? As I said, I've been using NWNX for years and have never seen it. Also, does anyone have any recommendations for configuration for a dual-core machine?

Thanks.

[FunkySwerve]

That's what happens when the ms int wraps because the number is too big to fit in the int field. IIRC it's limited to the same number as the Bioware int field, around 2.1 billion. Unless your mod has been up a long time, that's a sign that you need to streamline that script.
Funky

[william_hunter]

Also, NWN is single threaded, and there have been some reports of similar problems on the bio forums. There is a CPU affinity setting in the nwplayer.ini that you can use to bind the game to one core.

Here is a link

http://nwn.bioware.com/forums/viewtopic.html?topic=445423&forum=49&sp=0
_________________
The Realm of Tharagon NWN PW

[Papillon]

I have no link for you right now, but I think there was a problem with dual core CPUs at some point in time, where threads would switch from one core to another (scheduled by the uh.. scheduler) and the internal CPU timer was not synchronized between the cores. So, the time would jump back and forth and weird things would happen. Fixing to one core would help in this case.

Also, I would disable all PowerNow! and other power saving options.
_________________
Papillon