HWBOT
  1. HWBOT
  2. HWBOT-611

Spike: investigate icecat catalogue to improve hardware database

    Details

    • Type: Epic Epic
    • Status: Closed Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: hwbot v5.7.0
    • Labels:
      None

      Issues in Epic

      There are no issues in this epic.

        Activity

        Hide
        Frederik Colardyn added a comment -
        http://icecat.nl/menu/services/index.htm

        Seems exactly what we need and free! Very good find.
        Show
        Frederik Colardyn added a comment - http://icecat.nl/menu/services/index.htm Seems exactly what we need and free! Very good find.
        Hide
        Pieter-Jan Plaisier added a comment -
        Added this issue to Rev5. Especially if we will be adding smartphone benchmarks, this catalog will be interesting!
        Show
        Pieter-Jan Plaisier added a comment - Added this issue to Rev5. Especially if we will be adding smartphone benchmarks, this catalog will be interesting!
        Hide
        Pieter-Jan Plaisier added a comment -
        Fyi, I heard some rumours about Futuremark not looking into building rankings for Ice Storm and Cloud Gate (smartphone and tablet). I think we should the priority of smartphone and tablet support and at least try to feature rankings before Futuremark does?

        Show
        Pieter-Jan Plaisier added a comment - Fyi, I heard some rumours about Futuremark not looking into building rankings for Ice Storm and Cloud Gate (smartphone and tablet). I think we should the priority of smartphone and tablet support and at least try to feature rankings before Futuremark does?
        Hide
        Pieter-Jan Plaisier added a comment -
        Another high-quality Android benchmark application: http://www.quicinc.com/vellamo/test-descriptions/

        Vellamo can detect quite a lot of information from my device, even though not all information seems to be correct (eg: CPU speed). There are actually plenty of Android benchmarks that have quite a bit of technical information, including the device name, so I think we should mainly focus on getting our platform ready for supporting other platform benchmarks (not Windows) rather than figuring out how to get a perfect matching for our own benchmark application. That means:

        - populating the database with device information as well as technical information about the devices such as CPU type, GPU type, memory type, kernel and ROM.
        - preparing the application hierarchy so we can support comparison of platform, device and hardware (currently we only support hardware comparison)
        - expanding our benchmark api to provide android benchmark developers with an easy way to create benchmark rankings at hwbot

        The biggest problem I see is not really building the device database (maybe XDA even has that information available), but linking the hardware to the right items. Since HWBOT revolves around hosting all types of benchmarks, I think that will -always- be a main problem. If you're just hosting one benchmark, it's easy to make your strings match database entries, but different benchmarks might always have different strings. Imho, that is just a fact we will have to deal with and cannot easily work around. So, in my opinion, we will always have the manual labour of linking hardware to our database.
        Show
        Pieter-Jan Plaisier added a comment - Another high-quality Android benchmark application: http://www.quicinc.com/vellamo/test-descriptions/ Vellamo can detect quite a lot of information from my device, even though not all information seems to be correct (eg: CPU speed). There are actually plenty of Android benchmarks that have quite a bit of technical information, including the device name, so I think we should mainly focus on getting our platform ready for supporting other platform benchmarks (not Windows) rather than figuring out how to get a perfect matching for our own benchmark application. That means: - populating the database with device information as well as technical information about the devices such as CPU type, GPU type, memory type, kernel and ROM. - preparing the application hierarchy so we can support comparison of platform, device and hardware (currently we only support hardware comparison) - expanding our benchmark api to provide android benchmark developers with an easy way to create benchmark rankings at hwbot The biggest problem I see is not really building the device database (maybe XDA even has that information available), but linking the hardware to the right items. Since HWBOT revolves around hosting all types of benchmarks, I think that will -always- be a main problem. If you're just hosting one benchmark, it's easy to make your strings match database entries, but different benchmarks might always have different strings. Imho, that is just a fact we will have to deal with and cannot easily work around. So, in my opinion, we will always have the manual labour of linking hardware to our database.
        Hide
        Pieter-Jan Plaisier added a comment -
        Relevant information for smartphones (for enthusiasts):

        - Device
        --- Manufacturer
        --- Product (model number)
        --- Baseband version (depends on region)
        --- Hardware
        ----- SOC
        ----- CPU (type and frequency)
        ----- GPU (type and frequency)
        ----- Memory (type and frequency)
        ----- SD Card (type)

        - OS/Software
        --- Android version
        --- Kernel
        --- ROM

        For any device, the hardware fields will be fixed; so the hardware configuration we can get straight from the database (much like you can't change the chipset of a motherboard). The frequency and software information will be variable. The flash memory is something I'm not sure can be changed or known.
        Show
        Pieter-Jan Plaisier added a comment - Relevant information for smartphones (for enthusiasts): - Device --- Manufacturer --- Product (model number) --- Baseband version (depends on region) --- Hardware ----- SOC ----- CPU (type and frequency) ----- GPU (type and frequency) ----- Memory (type and frequency) ----- SD Card (type) - OS/Software --- Android version --- Kernel --- ROM For any device, the hardware fields will be fixed; so the hardware configuration we can get straight from the database (much like you can't change the chipset of a motherboard). The frequency and software information will be variable. The flash memory is something I'm not sure can be changed or known.
        Hide
        Dennis Devriendt added a comment -
        Icecat is gone, not enough relevant information. Maybe we will use pdadb.net, pending a response from them what the terms are for using their data. They seem to have a complete list with cpu/gpu/ram specs so definitely more useful for us.

        As for the rankings, a seperate ranking category for mobile, which ranks according to mobile device seems to be the best option. The hardware specs could still be linked to the results by using pdadb, so that they can also rank in the normal cpu/gpu/mem rankings (using truly multiplatform benchmarks, like our own benchbot).

        Flagging as impedement until we get a pdadb response.
        Show
        Dennis Devriendt added a comment - Icecat is gone, not enough relevant information. Maybe we will use pdadb.net, pending a response from them what the terms are for using their data. They seem to have a complete list with cpu/gpu/ram specs so definitely more useful for us. As for the rankings, a seperate ranking category for mobile, which ranks according to mobile device seems to be the best option. The hardware specs could still be linked to the results by using pdadb, so that they can also rank in the normal cpu/gpu/mem rankings (using truly multiplatform benchmarks, like our own benchbot). Flagging as impedement until we get a pdadb response.

          People

          • Assignee:
            Dennis Devriendt
            Reporter:
            Frederik Colardyn
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: