Opened 5 years ago

Closed 4 years ago

Last modified 4 years ago

#109 closed enhancement (fixed)

validation speed (Verarbeitungsgeschwindigkeit des Validators)

Reported by: martin.lehnert Owned by: birgit.jaekel
Priority: normal Component: XML Schema Validator
Version: 1.1 Keywords:


comments by JBV (Torben Brand) to alpha version:

Validator is incredibly slow. Validating a 107 MB file took 44 minutes. Using the Xerces2 java library, the same file was correctly validated in 20 seconds. If an internal representation of the contents is built while validating, the user should be able to choose between 'Validate' and 'Validate and load'.

Change History (4)

comment:1 Changed 5 years ago by martin.lehnert

  • milestone set to Productive version (V1.0)
  • Owner set to birgit.jaekel
  • Status changed from new to assigned

result of phone call with Torben (2015-05-08):

speed of validation process is slow --> check again how to speed up

comment:2 Changed 4 years ago by birgit.jaekel

Answer to Toben Brandt:

We have tested and validated the file you sent to us with the newer version of RailVIVID we have here for developing and we are glad to say that it took far less than 44 minutes to validate it.
We use Xerces for validation, but what takes long is the creation of the table rows. So the validation is finished after seconds and lines are added to the table as soon as errors occur, but these requests are polled and take some time. We plan to add a text label to the validation screen header which indicates that the validation has finished. With this, one can start the validation and will know if all errors are in the table when he comes back later. Until all of the 604980 errors where loaded to the table it took some time.
But maybe it’s not worth to invest a big effort in making it possible to show so many errors to the user. Nobody will be able to handle 1.000.000 errors at once. Maybe – in the next version - we should start grouping them when they become too many.
But for now we are able to validate the file and show the errors in the table in about 20 seconds.

comment:3 Changed 4 years ago by birgit.jaekel

  • Resolution set to fixed
  • Status changed from assigned to closed

comment:4 Changed 4 years ago by railML-admin

  • milestone Productive version (V1.0) deleted

Milestone deleted

Note: See TracTickets for help on using tickets.