N-o sa actualizez codul din articol, pentru ca l-ar face un pic prea complicat. Dar, cand voi avea data viitoare nevoie de executii mai rapide, imi va prinde bine.

Mersi!

O sugestie: trebuie neaparat sa cache-uiesti controalele daca poti.

De exemplu:

if (!cache[rowNo])
cache[rowNo] = document.getElementById(repeaterId + ‘_ctl’ + rowNo + ‘_lblPercent’);
cache[rowNo].innerHTML = percent;

Incerca sa vezi performanta. E o diferenta imensa dupa prima accesare.

Sper sa iti fie de ajutor tip-ul

BR,
Adrian Vintu

PS daca ai cumva un mobil Android (sau colegii), poti sa intri aci http://dex.adrianvintu.com pentru niste aplicatii de ale mele

I’ve put your code into my solution. I had to change just some minor things, like using “span” in JS instead of “label” (the Label in asp.net renders as a span) and checking for ” and NaN when adding values.
Anyway… It is a nicer approach, but it’s still slower than going after their built-up IDs, with the most basic methods.
My bechmarking was not the most thouroughly, but still (execution time of the “update calculations” method):
My basic JS way:
- IE8: ~17ms
- IE8-CM: ~22.5ms
This jQuery approach:
- IE8: ~143ms
- IE8-CM: ~170ms
(CM – Compatibility Mode)

It’s not at all too much for this example, but for a big form I had at work, it takes like 1 sec for the full calculations. And 2 sec would be too much.

I do have to admit the jQuery-newbie in me learned some stuff from your code.

$('tbody tr').each(function(i, item) {
var $item = $(item);

$item.find('label').text(percentage);
});

That will select everything with getElementsByTagName, which is fast even in IE6. You’d just need to change your markup slightly, wrapping the Repeater in a tbody so it’s faster/easier to exclude the heading rows.

I put a rough example up on JSBin. It could use some refactoring, but should perform decently: http://jsbin.com/izexu/edit