Loading... please wait.

Identification


not a member? register lost password? retrieve

quick search

compare processors

clear box browse processors

compare videocards

clear box browse videocards

stats

# results today: 223 # results total: 188725 # teams: 614 # users: 11375 # members: 12318 # bots: 986 hwbot engine: 2.1 666
 

External client API

About

We offer an external interface for 3rd party applications to submit the benchmark results directly to hwbot. Using this feature in your benchmark application will greatly improve popularity amongst the overclocking and hardware enthousiast community, and saves you the immens effort of building an online result comparing system.

This service is free of cost. To acquire assistance with implementing this interface, please ask either in our forums, or contact the hwbot development team.

How does it work?

The hwbot v2 engine supports external submission by an HTTP POST or GET request with a specific set as parameters that are either part of the url, or in the POST body.

After your benchmark has run, make an HTTP POST/GET to 'http://www.hwbot.org/submit.client.result.do' with the parameters described below, preferably using a IE/FF/Safari browser. The hwbot server will respond with an information page about the result. An interface which responds with a result code instead of html code can be built upon request, but for now it is ment to be submitted by a browser, like 3Dmark products.

The parameters.

parameter type length required example description
essentials
client text 255 yes the identification string of your client application wPrime
clientVersion integer yes the version of your client application 1.43
applicationId integer yes your benchmark application specific id. This number will be established by hwbot prior to integration. 15
score float 10 + 2 digits yes the benchmark result, a floating point number. Beware that hwbot only stores the number up to an accurary of 2 numbers after the digit. Eg 12.809 gets rounded to 12.81. 60.43
checksum text 255 no the checksum to verify the validity of the score. algorithm must be known by hwbot prior to integration. anything
verificationUrl text 255 no the external url where the benchmark score can be verified. if you host a online compare system of your own, use the direct link to the result http://futuremark.com/compare.do?id=1234
description text 255 no optional (short) description of the benchmark run, entered by the user. A longer description can be given after submission. my selfmade system: E6600 + zalman cooling
processor information
cpuId integer no (*) the id of the processor used. a list of known processors in xml can be retrieved here 1024
cpu (**) text 255 chars no cpu identification string, will be ignored if cpuId is given. hwbot engine will try to match the string to a known processor. Intel(R) Core(R) 2 E6600
cpuclock float 255 chars no the clockspeed, in mhz, the processor is running at 2950.60
videocard information
gpuId integer no (*) the id of the videocard used. a list of known videocards in xml can be retrieved here 886
gpu (**) text 255 chars no the videocard identification string, will be ignored if gpuId is given. hwbot engine will try to match the string to a known videocard. ATI Radeon(R) 9800 Pro 128mb
gpucoreclock float no the clockspeed, in mhz, the core of the videocard is running at 450.90
gpumemclock float no the clockspeed, in mhz, the videocard memory is running at 820.50
memory information
memTypeId integer 255 no (*) the id of the type of memory used. a list of known memory types in xml can be retrieved here. 2
memType (**) text 255 no the memory type. The hwbot engine will try to match this to a known memory type. DDR2
memRatingId integer 255 no (*) the id of the type of memory rating used. a list of known memory ratings in xml can be retrieved here. 3
memRating (**) text 255 no the memory rating. The hwbot engine will try to match this to a known memory rating. PC5300
memSize integer 255 no the size, in megabyte, of the total system memory 2048
memClock float 255 no (*) the clockspeed, in mhz, the system memory is running at. Warning: use real speed, not double in case of ddr. 266.66
memTCas float 255 no memory cas latency 2.5
memTRCD integer 255 no memory tRCD 2
memTRP integer 255 no memory tRP 2
memTRAS integer 255 no memory tRAS 5
memT integer 255 no memory T (1T or 2T) 1
memTimings text 255 no Mem timings will only be parsed when tCas, tRCD, TRP, TRas, t is empty. Accepted formats: CL2 2-2-5 1T or CL2 2-2-5 or CL2.
Regular expression:
^CL([0-9.]{1,3})$, ^CL[ ]([0-9.]{1,3}) ([0-9]{1,2})-([0-9]{1,2})-([0-9]{1,2})$, ^CL[ ]*([0-9.]{1,3}) ([0-9]{1,2})-([0-9]{1,2})-([0-9]{1,2}) ([12])T$ 		CL2.5 2-2-5 1T
memory info
mbId integer 255 no (*) the id of the type of motherboard chipset used. a list of known chipsets in xml can be retrieved here. 5
mbChipset (**) text 255 no the motherboard chipset. The hwbot engine will try to match this to a known chipset. Intel P965
mbModel text 255 no The motherboard model name. Gigabyte P965 DS3
mbVendor text 255 no The name of the motherboard manufacturer. ASUS

(*) althought no error will be returned when the parameter is missing, it is highly recommended to supply this parameter if this hardware is tested by your benchmark application. eg. if you have a benchmark application which tests both the processor and videocard, supply both cpu(Id) and gpu(Id) and optionally the clock frequency too if known.

(**) this parameter will be ignored if the corresponding 'Id' parameter is not empty. Eg. if you supply the correct cpuId, the hwbot engine will not try to parse the cpu string to a known processor.

  

Country rankings

1. flag of RUSSIAN FEDERATION Russian Federation
2. flag of GERMANY Germany
3. flag of UNITED STATES United States
4. flag of GREECE Greece
5. flag of ITALY Italy
6. flag of FRANCE France
7. flag of UNITED KINGDOM United Kingdom
8. flag of POLAND Poland
9. flag of UKRAINE Ukraine
10. flag of AUSTRALIA Australia

HWBOT Records

CPU-Z:
Flag of italy 8179.89 mhz »
PCMark 2005:
Flag of united states 27601 marks »
PiFast:
Flag of greece 15.69 sec »
SuperPi:
Flag of latvia 7.41 sec »
SuperPi 32m:
Flag of italy 8min 1sec 480ms »
wPrime 1024m:
Flag of united states 1min 52sec 250ms »
wPrime 32m:
Flag of united states 3sec 450ms »
3Dmark 2001:
Flag of australia 118076 marks »
3Dmark 2003:
Flag of greece 98063 marks »
3Dmark 2005:
Flag of united states 38391 marks »
3Dmark 2006:
Flag of greece 30045 marks »
Aquamark:
Flag of united states 350050 marks »