OS4 DepotLogo by Nickman 
(anonymous IP:,549) 

   Bug tracker
   Locale browser

   o Audio (323)
   o Datatype (47)
   o Demo (176)
   o Development (489)
   o Document (19)
   o Driver (85)
   o Emulation (133)
   o Game (809)
   o Graphics (429)
   o Library (79)
   o Network (186)
   o Office (51)
   o Utility (746)
      o Archive (60)
      o Benchmark (12)
      o Communication (3)
      o Docky (18)
      o Filetool (120)
      o Hardware (20)
      o Misc (141)
      o Print (7)
      o Scientific (31)
      o Script (23)
      o Shell (91)
      o Text (87)
      o Workbench (133)
   o Video (55)

Total files: 3627

Full index file. Download
Recent index file. Download



Support the site

 Readme for:  Utility » Benchmark » c-ray.lha


Description: Simple raytracing tests
Download: c-ray.lha       (TIPS: Use the right click menu if your browser takes you back here all the time)
Size: 226kb
Version: 1.1
Date: 27 May 11
Author: John Tsiombikas, Ian Mapleson, AmigaOS 4 compile by Varthall/Up Rough
Submitter: Varthall/Up Rough
Homepage: http://www.futuretech.blinkenlights.nl/c-ray.html
Category: utility/benchmark
License: Other
Distribute: yes
Min OS Version: 4.0
FileID: 6446
Comments: 0
Snapshots: 0
Downloads: 211  (Current version)
211  (Accumulated)
Votes: 0 (0/0)  (30 days/7 days)

Show content Show crashlogs Replace file 
C-Ray Simple Raytracing Tests
By: John Tsiombikas <nuclear()siggraph.org>
Test suite compiled by: Ian Mapleson <mapesdhs()yahoo.com>
Last Change: 10/Apr/2008

C-Ray is a simple raytracer written by John Tsiombikas; in his
own words, it is:

  "...an extremely small program I did one day to figure out how
  would the simplest raytracer program look like in the least
  amount of code lines."

The relevant discussion on Nekochan is at:


The default data set is very small, so C-ray really only tests the pure
floating-point (fp) speed of a CPU core (or multiple CPUs/cores using the
threaded version), ie. RAM speed is not a significant factor. John said:

  "This thing only measures 'floating point CPU performance' and
  nothing more, and it's good that nothing else affects the results.
  A real rendering program/scene would be still CPU-limited meaning
  that by far the major part of the time spent would be CPU time in
  the fpu, but it would have more overhead for disk I/O, shader
  parsing, more strain for the memory bandwidth, and various other
  things. So it's a good approximation being a renderer itself, but
  it's definitely not representative."

Nevertheless, the results are certainly interesting:

If you wish to submit your own results, follow the instructions given
below. Send the data to me, not to John, and I will add them to the
relevant tables; please include all requested details.

Comments and feedback welcome!



File Version Size Date OS Dls Readme
cubebm.lha1.028kb16 May 084.0795¤ Cubebm - MiniGL Cube with benchmarks
Copyright (c) 2004-2015 by Björn Hagström All Rights Reserved
Amiga OS and its logos are registered trademarks of Hyperion Entertainment