CCPulse on Dual Core

[DarkAngel]

Hi all

I've just ordered a bunch of new pc's for my department, since the old one's are all out of warranty, and the spec of them is terrible

The new machines are all dual core processors - Does anyone know of any way of configuring the machines and/or CCPulse to get the best out of the dual core systems?

I know they will run better because one core will handle XP, and the other will handle pulse, but does anyone know of any other "tricks" that could be employed?

DA

[tony]

I really can't say that much about "dual core" Intel Processors for XP/CCPulse and I would be interested to know how you might set (the BIOS?) to have the OS on "one core" and then CCPulse "on the other".... sounds intriguing!

I [b]do[/b] know that there is a start-up parameter you can apply to CCPulse that might help you.  You would need to create a .BAT file, to start CCPulse so that it cannot eat away at the majority of the available memory, as follows;

CMD.EXE /C start /BELOWNORMAL C:\GCTI\CCPulse\CallCenter.exe


I hope this helps?

Tony

[victor]

[quote author=DarkAngel link=topic=3790.msg16278#msg16278 date=1233309147]
Hi all

I've just ordered a bunch of new pc's for my department, since the old one's are all out of warranty, and the spec of them is terrible

The new machines are all dual core processors - Does anyone know of any way of configuring the machines and/or CCPulse to get the best out of the dual core systems?

I know they will run better because one core will handle XP, and the other will handle pulse, but does anyone know of any other "tricks" that could be employed?

DA
[/quote]

I have not heard anywhere yet that Genesys CCPulse would work better if you specify which core you run it on. Usually, based on what I have seen and known so far, it is highly unlikely that you could segment XP to one core in a first place, unless you specify this in your startup parameters. Of course, if you do that, then all of your applications will run on the same core as XP anyway, so there is no real advantage to that.

By default, Windows is distributing processing between two or more cores based on rather complicated algorithm that I was unlucky enough to try to temper with. What I have learned from my experience is that most of the times, it is impossible to:
1. specify which core process will run on
2. specify how the cores are used by different threads within application

Starting with .NET 1.0, threads for any process will AUTOMATICALLY be assigned to the same core as the parent process. CCP is seen as one process with quite a few threads (check it with Thread Viewer, and you will be really amazed on how it works!!! Those guys really did a great job starting with 7.5! ) thus it will be all running on the same CPU all the time. And since XP cannot be assigned to any particular CPU, there is little chance of being able to divide CCP and XP system as far as I know.

If this is not true, I definitely would like to know it so that I can take advantage of this as well!!!

[tony]

Vic, ditto for both of us, to this statement, I think:

[i]"I know they will run better because one core will handle XP, and the other will handle pulse, but does anyone know of any other "tricks" that could be employed?"[/i]

News to me that you could do that...

Tony