Multi core CPUs

[PhotonDemon]

Hi All,

For as long as I can remember, it has been strongly recommended that the team mode of development (ENVY server) not be used on multiprocessor Windows systems. I develop alone, so this is fine with me but now that multi core CPUs are everywhere, I am wondering what the underling problem is and if it can affect packaged programs. Can someone please describe the problem and if packaged programs running on multi core Windows systems are safe?

Lou

[marten]

This was a emsrv (the envy server application) problem ... not a general VASmalltalk problem.

Marten

Hi All,

For as long as I can remember, it has been strongly recommended that the team mode of development (ENVY server) not be used on multiprocessor Windows systems. I develop alone, so this is fine with me but now that multi core CPUs are everywhere, I am wondering what the underling problem is and if it can affect packaged programs. Can someone please describe the problem and if packaged programs running on multi core Windows systems are safe?

Lou

[PhotonDemon]

Hi Marten,

Thanks for the reply. I remember that it was an emsrv problem but I thought it was caused by a Windows problem that couldn't be circumvented by emsrv. Otherwise, IBM and or Instantiations would have fixed it?

Lou

[koschate]

Lou the multi-cpu problem is described in the FAQ: http://www2.instantiations.com/VAST/Doc ... mserv.html but, as Marten said, it doesn't affect Smalltalk programs anyway.

Tom

[PhotonDemon]

Hi Tom,

Thanks for the reply. The description under "Problem" was very helpful. I know that it was always claimed that Smalltalk programs were not effected but without understanding the underling cause, I didn't know if I could trust that claim. I was imagining that some odd-ball timing problem could cause trouble with packaged programs. Thanks.

Lou

[tc]

Hello,

A long time ago, I think OTI was responding to the problem of corrupt repositories. The issue appeared with Windows and multi-core hardware. However, I do not think OTI actually pinpointed a precise 'root cause', ie a defect in Windows or Emserv but speculated (as the link above describes).

--tc