Hardware sizing... how to approach it...

This forum deals with administrative topics such as monitoring and system setup. It is dedicated to system administrators who do not have to deal with the functions themselves but who have to establish and maintain proper environments.
Public since 15.2.2017

Hardware sizing... how to approach it...

Postby Asterix » Mon Jul 17, 2017 2:36 pm

Hi there,

from time to time we (consultants and supporters) get asked for hardware recommendations. Here are just some lines describing what we can provide but also where we might have a gap:

Feel free to assemble that information in your mind and to get back to us if you have questions:
  • Standard benchmarks: our developers are running benchmarks with the services they provide. For this purpose we use documented hardware, various operating systems and - what is quite important - a defined set of scenarios for each service, e.g.
    • xLocate: addresses with country codes, ..
    • xRoute: waypoint coordinates with short (50-km) /medium / large (1000km+) distances...
    • xMap: coordinate rectangles with fixed sizes (256^2, 400^2, ...)
    • xTour: planning scenarios (small versus complex)
  • While some of these performance results are then easily to be adapted to your usecases (e.g. computation of map rectangles scales more or less linear with the number of pixels if you keep the other values (ok, there might be some sideeffects)) others (xTour) are not that easy to match.
  • xTour scenarios: there are many different options that have their own impact on performance / throughput in the xTour context. Follow the questions and you can see that it is difficult to recommend some hardware based on our standard benchmarks only.
    • Do you clean your distance matrix with each request?
    • Distance type: Do you use airline, traditional routing or highperformance routing?
    • What is the number of orders you plan? (most users expect this number to be sufficient for a recommendation)
    • Which one of the planning steps are enabled?
    • How do you use the AMT (=AvailableMachineTime)?
    • How many time windows are applied to the orders or vehicles?
    • Which planning scenario do you apply (Standard? Balancing?...)
    • How many skills do you define?
    • ...and some more...

Therefore I usually tell customers that we have to enable them to perform their own benchmarks reflecting their own scenario. We provide
  • tools (XServerRequestRunner and more)
  • knowledge
to teach you how to "fish".

In the end it is once more a question of communication:
Get in touch with your local PTV experts and they'll have a look at your data and tell you how to stress an existing system. But please be aware that even our own developers would require YOUR data processed in a transaction based on YOUR APPLICATION on YOUR hardware to recommend how many machines you need and to evaluate whether the existing hardware is configured properly.

So far from here, we look forward to your feedback!

Bernd Welter
Manager Technical Consulting & Requirement Engineering
Senior Technical Consultant Developer Components
PTV GROUP - Germany

User avatar
Site Admin
Posts: 740
Joined: Mon Apr 14, 2014 10:28 am

Return to PTV xServer Administration