ASP.Net Validators and performance issues

[Guest]

Hi All,

In one of the project discussions, one team member raised a question whether
the usage of asp.net validation controls (like RequiredFieldValidator,
CustomValidator, RegularExpression Validator etc) would cause any performance
issue for the application ? Can someone give some ideas whether the usage of
these controls will downgrade the performance of the asp.net web application.

Thank you
Suhas

 

[Brendan Green]

Don't they run on the client? If so, I would imagine that the performance
impact would be negligible.

 

[Guest]

Depending on the number of validators on a page and the length of your unique
control names there can be an impact on the rendered page size.

 

[Guest]

There are performance issues but almost negligible, the pick of them is

It downloads a JS file to the client, which is a burden on your wire.
Other wise there are many features they provide offcourse saving lots of ur
precious time.

 

[Ray Booysen]

All validators support server-side and client-side validation. As
client side validation can be disabled, you need to have a server side
implementation to cover this case.

Regards
Ray

 

[Roland]

There _is_ a remarkable performance issue with an increasing number of
validators under .NET 2.0. (not tested with 1.1).

I had a page containing 55 validators, all client side validators, all kinds
together (Required, Custom, RegExp). There was such a big impact to the
initial page load time and the page load time after postback, that I had to
drop this and return to a server side validation. The crux wasn't the
runtime of the validators itself, but the loads and setups. There was a
horrible, .net made JS nightmare in the source code view of my page, which
already gave an impression of the load time desaster.

The issue wasn't server based, but completely client made. I have a machine
(1.4 ghz P4, IE6), which isn't the fastest due to all the dev things I have
on the box.

Probably the situation became worse over here, because I had to implement a
bunch of custom validators, each of them validated more than one control at
a time (you know the ValidatorHookUpControlID things and stuff).

The performance break wasn't that dramatic with FireFox...

Regards