|
|
|
Why KribiBench ? The essential task in the final phase of the development of a 3D rendering engine, much like for a racing car engine, is tuning for the best possible performances on actual machines. After each small change in the program code, very precise timings show us the amount of speedup achieved (if any). For this purpose, we time with a stopwatch the rendering of a sequence of images, the laps of our racecourse. For a given version of the Kribi 3D Engine, these timings can also be used to compare the performances of diverse computers, i.e. our stopwatch can be used as a benchmark application. Our marketing team has identified here a good opportunity to catch public eyes on the Kribi project by releasing a useful freeware, KribiBench was born this way. In the early days of the KribiBench we were missing the very last hardware from the diverse key providers in our labs, and instead of buying a new machine every 2 weeks, we have had the idea to contact a few so-called computer hardware sites to let them do the benchs for us… It worked ! One site was kind enough to endure Alpha versions of the KribiBench and has even published the first ever public KribiBench scores. Have a look at Ace's Hardware to meet these brave testers and to have access to fine and independent informations about hardware devices from all players in the market. Since the first phase of the KribiBench in Q3’2001 we have released the pack to a large gang of betatesters, all around the world. In parallel with our most important task, enhancing the Kribi Renderer, KribiBench has evolved following their remarks, many thanks guys !
|
|
Version 1.1 available!
If you publish KribiBench scores it will be nice to let us know Public Scores
Hot Hardware
Tech Report
|
