PerformanceTest V8 Feature List

[tehcheese]

• Better baseline search [Done on client, 30% done in cloud]

could you further elaborate on this? the reason i ask is because along with the "Sort by" function in the "Advanced Search" feature, it would be good to have an option added to only show values of a specific range(greater than/less than). It would be convenient for someone like me who use G3D scores when upgrading my graphics card to shoot for a good/reasonable G3d mark to better plan what my new setup should be like and also get to look at the different setups i find under this range. Yes i can use the select page function but its a bit tedious to pin down a range i want, not to mention the majority of "The Connection to the Internet timed out" errors that i get when doing it this way.

[David (PassMark)]

Thanks for the suggestion.

The problem with including the ability to do a ranged search on G3D is that it is the thin edge of the wedge. It wouldn't make sense from an interface point of view to do it just for this one value. What about the CPUMark, 3Dmark, Diskmark, etc..
On the other hand doing it for every value would result in a much more complex data entry field. The form would be too large to fit on some monitors.

Given there is a work around of doing a sort and then just ignoring the unwanted results, I don't think the added complexity justifies the benefit.

More interesting (for us) is the 'time out' message. This should only happen if the search takes longer than 15 seconds. I did some searches here today but we couldn't get any search to take this long. More typical was search times around 4 sec. What was the search criteria you are using to generate this long searches? If there really are searches taking longer than 15 sec then we need to fix it. It could of course be some other issue, like a bad Wireless connection to the internet.

[tehcheese]

It wouldn't make sense from an interface point of view to do it just for this one value. What about the CPUMark, 3Dmark, Diskmark, etc..

Yes i know it would make sense to do it for the other scores, i was just using G3D as an example.

On the other hand doing it for every value would result in a much more complex data entry field. The form would be too large to fit on some monitors.

Well the way i was thinking it could be implememnted would be just one checkbox that reads, "Show values under this range", when checked this checkbox could enable a dropdown box with the options "lesser than" and "greater than", then beside this dropdown box would be a textbox for the desired range input. Also note that this checkbox could be disabled until the user chooses a sort option that sorts by some kind of numerical value(score) because this range search obviously wouldn't work for the other stuff like "CPU Type" and that sort.

More interesting (for us) is the 'time out' message. This should only happen if the search takes longer than 15 seconds. I did some searches here today but we couldn't get any search to take this long. More typical was search times around 4 sec. What was the search criteria you are using to generate this long searches? If there really are searches taking longer than 15 sec then we need to fix it. It could of course be some other issue, like a bad Wireless connection to the internet.

I'm on an ethernet connection. I usally get this error when I switch to the advanced tab, then under "Sort by", choose some score then hit search. The initial search is usually flawless but when i attempt to do a huge page change; like selecting the 1400th page on the page select box, that's when i get the error, smaller changes from one page to the page right after that usually works but that is somewhat slow and sometimes i still get the error. might just be my connection idk.

Lastly thanks for the reply, i understand it isn't very beneficial vs. the complexity. I just thought it would be good to have. I really like all of your software, every single software made by Passmark is made to perfection. Also looking forward to the beta release of Performance Test

[David (PassMark)]

Was able to reproduce the timeout here. So it isn't your connection.
Workaround for the moment is to reduce the scope of the search. e.g.
Select a date range, or a CPU type, etc..

The problem is that not all fields are indexed in the database. So some queries which depend on non indexed field results in linear search and then a time consuming sort. Indexed fields are pre-sorted so don't have this problem. But making all fields indexed would significantly increase the size of the DB and slow down other operations. Anyway we'll take a deeper look next week and work out the best solution.

[David (PassMark)]

Another development update on PT8.

We are just finishing testing an internal alpha release at the moment.
We should have a beta release available next week, Mid Aug 2012.

I have also update the post at the top of the thread with some new details.

Update: the beta of PT8 is now available to the public.
I will close this thread. Any comments on the PT8 beta should be made in the new thread above.