New BenchDB – Development iteration # 84

Apr

20

2016

The developers have released iteration # 84. The attention was in the past three weeks on the preparation of the new BenchDB to go live. In addition, we are working on the implementation of HTTPS and HTTP / 2.

new BenchDB

Tweakers since 2004 has a database with benchmarks. The editors used the BenchDB to manage test results and generate graphs to display test results in reviews. The old BenchDB had its own entrance to the site which you could look up and compare benchmark results.

The location was BenchDB by yours truly hacked together and later feature enhancements, including the ability to generate multi-value charts. The hastily written code was never of high quality and is subsequently no longer touched. As a result, the BenchDB was not in any way integrated with the rest of Tweakers. The management even went through our old CMS, which was designed at the time of the millennium.

For the editors showed the capabilities and usability rather poor. Thus, it was not possible to quickly generate graphs of different tests for the same set of products and the composition could from a once-generated graph are not changed later. Another problem was the lack of good connections with products. It was therefore not possible to display super relevant test results in the product area.

BenchDB old cms

Entering test results in our vintage-cms

Plans to build a new BenchDB existed for a long time, but due to the size of the project was the long wait for space in our roadmap to implement the project. Because of the state of the code required a complete rewrite. Beginning in 2015 the first piece of the project was carried out and after the work on the BenchDB had stopped for a while, we have been working since October 2015 to specify each iteration gradually the functionality in the BenchDB and rewriting. After many sprints work that is invisible to our users, we have finally come so far that we can see the first results of the new BenchDB.

The new BenchDB is now fully built in Symfony and the entities in the BenchDB where possible, by means of categories and products from the Pricewatch. Test data are now stored better structured. Thus, it is possible to store and automatically to calculate the averages on different runs of the same benchmarks for “test object” (a product which has been tested under a certain circumstance). The editors’ ability to generate charts and graphs management is made easier. So editors can now create an article sets of test objects and generate a few clicks graph tags that can be inserted into articles.

new BenchDB

The tags are converted to dynamic while parsing the page in a graph. Most of the types of graphs can be generated by means of the c3.js. Also, we have to generate the possibility of bar graphs, with in addition to the product name of a type of test condition or a specification as a column. The specification is automatically retrieved from our product database. Test condition types describe a situation where a product was tested, for example, the version of a driver or operating system or processor to a graphics card was tested.

Web browsing (@ Brightness 250cd / m2),watching videos (@ Brightness 250cd / m 2)
521
592
407
566
Webbrowsen(helderheid @250cd/m2)
in minuten hoger is beter
0
100
200
300
400
500
600
Apple iPhone 6S Plus
Samsung Galaxy S7 edge
Wileyfox Swift
iPhone SE
Accuduur
A graph that has been generated by the new BenchDB

In the next iteration, we continue working on phasing out the BenchDB so the old code eventually as a whole to / dev / null can be discharged. In three weeks we will add a simple view of the test results on the specificatietab in the product area. With this you can just as easily look up the test results of a product’s specifications. In the near future there for editors also get some feedback on work underway to link old test results of products in the Pricewatch.

And then we have …

worked on the implementation of HTTPS and HTTP / 2, so that you can look into the future through a secure and efficient protocol Tweakers;
progress with the upgrade to PHP7;
Usabilla the feedback button accessible on mobile devices and the default tracker put on meescrollen so the feedback button on desktops and tablets with a horizontal resolution of 1024 pixels no longer lies on the margin of the content;
a successful first April Fool’s joke put live;
We have solved about thirty bugs in a bug bash.

Viewing:-121

In: Technology & Gadgets Asked By: [15229 Red Star Level]

Answer this Question

You must be Logged In to post an Answer.

Not a member yet? Sign Up Now »