Licensing and mulithreading
Posted: Fri Jul 02, 2004 9:23 am
Hi guys
Heres the scenario.. Dell server 2650 that allows multithreading. Great! we have a DS7 installation that is licensed for two CPUs, which, on hardware level is what the Dell has - 2 CPUs (2 x 2.8 )
with multithreading, we will have 4 x 1.4. The problem as you can well imagine is that DS7 complains about the additional CPUs.
We eventually switched of multithreading to avoid the warnings and what-not.
Are we not penalising technology here? _Is_ licensing by CPU the best way to license DS, is number of developers not a better way? I am sure this has been debated many a time by Ascential, but for the developers out here/there - what is the justification? Is it just following market trends - i.e. "sounds like a good idea"?
I cant confirm this but I think Sun will have the ability to prohibit the OS from picking up what is happening with the CPUs, which will ruin the license by CPU strategy so many db vendors and Ascential are following.
...the reason to post this here I suppose is just to get some clarification from the people in the know, and some insight from the rest of the developers...
Heres the scenario.. Dell server 2650 that allows multithreading. Great! we have a DS7 installation that is licensed for two CPUs, which, on hardware level is what the Dell has - 2 CPUs (2 x 2.8 )
with multithreading, we will have 4 x 1.4. The problem as you can well imagine is that DS7 complains about the additional CPUs.
We eventually switched of multithreading to avoid the warnings and what-not.
Are we not penalising technology here? _Is_ licensing by CPU the best way to license DS, is number of developers not a better way? I am sure this has been debated many a time by Ascential, but for the developers out here/there - what is the justification? Is it just following market trends - i.e. "sounds like a good idea"?
I cant confirm this but I think Sun will have the ability to prohibit the OS from picking up what is happening with the CPUs, which will ruin the license by CPU strategy so many db vendors and Ascential are following.
...the reason to post this here I suppose is just to get some clarification from the people in the know, and some insight from the rest of the developers...