Skip to main content

Why is this Javascript much *slower* than its jQuery equivalent?



I have a HTML list of about 500 items and a "filter" box above it. I started by using jQuery to filter the list when I typed a letter (timing code added later):







$('#filter').keyup( function() {

var jqStart = (new Date).getTime();



var search = $(this).val().toLowerCase();

var $list = $('ul.ablist > li');



$list.each( function() {

if ( $(this).text().toLowerCase().indexOf(search) === -1 )

$(this).hide();

else

$(this).show();

} );



console.log('Time: ' + ((new Date).getTime() - jqStart));

} );







However, there was a couple of seconds delay after typing each letter (particularly the first letter). So I thought it may be slightly quicker if I used plain Javascript (I read recently that jQuery's each function is particularly slow). Here's my JS equivalent:







document.getElementById('filter').addEventListener( 'keyup', function () {

var jsStart = (new Date).getTime();



var search = this.value.toLowerCase();

var list = document.querySelectorAll('ul.ablist > li');

for ( var i = 0; i < list.length; i++ )

{

if ( list[i].innerText.toLowerCase().indexOf(search) === -1 )

list[i].style.display = 'none';

else

list[i].style.display = 'block';

}



console.log('Time: ' + ((new Date).getTime() - jsStart));

}, false );







To my surprise however, the plain Javascript is up to 10 times slower than the jQuery equivalent. The jQuery version takes around 2-3 seconds to filter on each letter, while the Javascript version takes 17+ seconds! I'm using Google Chrome on Ubuntu Linux.





This isn't for anything really important so it doesn't need to be super efficient. But am I doing something really dumb with my Javascript here?



Source: Tips4all

Comments

  1. You could try using textContent instead of innerText , I think it should be faster. Also timing the list-generation and loop separately would tell if there is problem in list-generation.

    ReplyDelete
  2. Another best practice for javascript speed is caching the list.length in a variable and calling the variable like:

    l = list.length;
    for (var i=0;i<l;i++):{ code here}


    And maybe timing with jsperf would be better.

    ReplyDelete
  3. I used while instead of for and did some minor improvements. Here is the final code.

    var list = list = document.querySelectorAll('ul.ablist > li');
    document.getElementById('javascriptFilter').addEventListener( 'keyup', function () {
    var jsStart = (new Date).getTime(),
    search = this.value.toLowerCase(),
    i = list.length - 1,
    listItem,
    result;
    while( i >= 0 )
    {
    listItem = list[i];
    if ( listItem.textContent.toLowerCase().indexOf(search) === -1 )
    listItem.style.display = 'none';
    else
    listItem.style.display = 'block';
    i--;
    }

    result = ((new Date).getTime() - jsStart);
    console.log(['Time: ', result, '<br />'].join(''));
    }, false );

    ReplyDelete

Post a Comment

Popular posts from this blog

[韓日関係] 首相含む大幅な内閣改造の可能性…早ければ来月10日ごろ=韓国

div not scrolling properly with slimScroll plugin

I am using the slimScroll plugin for jQuery by Piotr Rochala Which is a great plugin for nice scrollbars on most browsers but I am stuck because I am using it for a chat box and whenever the user appends new text to the boxit does scroll using the .scrollTop() method however the plugin's scrollbar doesnt scroll with it and when the user wants to look though the chat history it will start scrolling from near the top. I have made a quick demo of my situation http://jsfiddle.net/DY9CT/2/ Does anyone know how to solve this problem?

Why does this javascript based printing cause Safari to refresh the page?

The page I am working on has a javascript function executed to print parts of the page. For some reason, printing in Safari, causes the window to somehow update. I say somehow, because it does not really refresh as in reload the page, but rather it starts the "rendering" of the page from start, i.e. scroll to top, flash animations start from 0, and so forth. The effect is reproduced by this fiddle: http://jsfiddle.net/fYmnB/ Clicking the print button and finishing or cancelling a print in Safari causes the screen to "go white" for a sec, which in my real website manifests itself as something "like" a reload. While running print button with, let's say, Firefox, just opens and closes the print dialogue without affecting the fiddle page in any way. Is there something with my way of calling the browsers print method that causes this, or how can it be explained - and preferably, avoided? P.S.: On my real site the same occurs with Chrome. In the ex