Hi Przemek, Even I don’t have the latest version of Xbase++ but an old one I'm sure that they lock the application threads to use only one CPU. They have a way to choose which CPU to use (as an example the less used CPU). In older versions they have serious degradation in speed due to interlock between 2 or more CPUs. Also they have another speed penalty due to the use of som.Dll (If I remember correctly is a Visual age compiler dll). They have made performance analysis and they said that they are thinking to change C compiler and remove the som.dll. Only with this they said that the speed benefit it will be from 15% to 30%. Also about the Dbf speed the problem exist due to classify the underlying of the record.
Brgds Mike Evans -----Original Message----- From: harbour-boun...@harbour-project.org [mailto:harbour-boun...@harbour-project.org] On Behalf Of Przemyslaw Czerpak Sent: Saturday, March 28, 2009 9:21 AM To: Harbour Project Main Developer List. Subject: Re: [Harbour] Re: XBASE++ speedtst On Fri, 27 Mar 2009, Angel Pais wrote: Hi, > I'll do it in a while but AFAIK xbase++ only uses one processor per > process, if so it does not scale. > We'll confirm that soon It's not such easy to use only one CPU. In most of operating system it's not even possible. I would be very surprised if the above is true. Anyhow if you serialize too much things then you will reduce the performance to single CPU but it's only side effect of inefficient algorithms not intentional design decision and of course it does not mean that only one CPU is used. best regards, Przemek _______________________________________________ Harbour mailing list Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour _______________________________________________ Harbour mailing list Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
