Forum Coordinators: RedPhantom
Poser - OFFICIAL F.A.Q (Last Updated: 2025 Jan 24 6:22 pm)
Took the analysis one step further... Actually 3 of the 4 way above the bar don't need work per se, they are predictable. The slowest 2 are 256MB memory, the only 2 so configured, the next slowest is the OSX one (clearly an apples-vs-oranges comparison). The only one "off" is then the next which is a P3 933, which as the only P3 left in the set (the other was dropped as being > 650 secs) can't really be characterized. Of the 2 fast outliers, I can find no details behind the AMD 1.4 @ 234 secs (it appears first in Jim's "Results So Far.." post so perhaps it's been deleted/withdrawn?). On the AMD 2.1 at 192 are we seeing the AMD vs P4 clock speed issue? It looks to me as if most current AMD's have been tabulated at the speed indicated by the name - e.g. 2600+ as 2.6. This would make sense as the number is how AMD equates to Intel's current P4 somewhat-inflated GHz numbers (which assume that the big P4 pipeline is fully occupied - rare even with newest software, certainly not an old Mac app converted as a WIn 3.1 application ;-). So if this particular point is converted from actual GHz to P4-equivalent GHz that makes it a 2600, putting it as a close outlier to the grey band. Probably close enough for Jim to have included it when he created the band. Final interesting nugget, the P4 2.8 @ 253 outlier on the slow side is the only system at 512MB. So 512MB is the realistic minimum (with an NT-based OS) for this scene. Having less than 1GB does hurt a little but not much. Probably means the sweetspot for this .pz3 was something like 640MB? So overall a very tight spread, considering all the variablities involved. A very useful experiment, but unfortunately one that ultimately breaks down to nothing more than the old racers' motto: "There's no substitute for horsepower"!
This site uses cookies to deliver the best experience. Our own cookies make user accounts and other features possible. Third-party cookies are used to display relevant ads and to analyze how Renderosity is used. By using our site, you acknowledge that you have read and understood our Terms of Service, including our Cookie Policy and our Privacy Policy.
Mark