ICEfaces
  1. ICEfaces
  2. ICE-3217

Improved performance of MenuBar on IE6

          Details

          • Type: Improvement Improvement
          • Status: Closed
          • Priority: Major Major
          • Resolution: Fixed
          • Affects Version/s: 1.7.1
          • Fix Version/s: 1.7.2
          • Component/s: ICE-Components
          • Labels:
            None
          • Environment:
            Icefaces 1.71, Websphere 6.02, Windows xp

            Description

            I have prepared a very simple test case to show the performance-bug over MenuBar. This is a clean example, only menubar is displayed in a page.

            Is a quite big menu (but not very big) where every option goes from default test1.iface to test2.iface. The test pages have only a label showing either test1 or test2

            Response times to change from page test1 to test2 are:

            Firefox 2: < 1 s
            Internet Explorer 7: 1s
            Internet Explorer 6: > 10s !!!

            As you will be able to see, using menuBar component is not suitable in IE6 !! due to very bad performance.
            I must clarify that this behavior was not happening in 1.7 DR3. This performance issue started after 1.7.0

            I am attaching MenuBugTestCase.war.

            Regards.

              Activity

              Ascending order - Click to sort in descending order
              Hide
              Permalink
              Nicolas Erlijman added a comment -

              MenuBar Bug test case. Lib files are not attached.
              Using sun jsf 1.1 and Icefaces 1.7.1

              Show
              Nicolas Erlijman added a comment - MenuBar Bug test case. Lib files are not attached. Using sun jsf 1.1 and Icefaces 1.7.1
              Hide
              Permalink
              Nicolas Erlijman added a comment -

              I have to correct, in IE it is not 10s, it is like 4s. Have modified IE6 preferences to its defaults to make sure It wasn't IE configuration problems.
              Anyway, 4s is still unacceptable for production applications.

              Show
              Nicolas Erlijman added a comment - I have to correct, in IE it is not 10s, it is like 4s. Have modified IE6 preferences to its defaults to make sure It wasn't IE configuration problems. Anyway, 4s is still unacceptable for production applications.
              Hide
              Permalink
              Walter Fernandez added a comment -

              I have the same problems that Mr. Erlijman with IE. MenuBar component have very bad performance.

              Regards.

              Show
              Walter Fernandez added a comment - I have the same problems that Mr. Erlijman with IE. MenuBar component have very bad performance. Regards.
              Hide
              Permalink
              Alejandro Perez added a comment -

              it will be really great if you can solve this, I am actually having performance problems because of this inconvenient. Thank you in advance

              Show
              Alejandro Perez added a comment - it will be really great if you can solve this, I am actually having performance problems because of this inconvenient. Thank you in advance
              Hide
              Permalink
              Adnan Durrani added a comment -

              trunk: revision 17020
              branch 1.7: revision 17021

              Can you please re-test your application?

              Show
              Adnan Durrani added a comment - trunk: revision 17020 branch 1.7: revision 17021 Can you please re-test your application?
              Hide
              Permalink
              Nicolas Erlijman added a comment -

              I have re-tested with that branch and the 3-4 sec delay is fixed. Anyway I have 2 comments.

              1. Overall performance is slower than 1.7DR2. Also in FF is a bit slower. I test both libraries with same code and 1.7DR2 is faster.
              2. Autocomplete in IE is very very slow compared to FF. There is same kind of delay of the menu, when you press some key, there is like 3 secs delay for the div to appear. In FF is much quicker.

              regards.

              Show
              Nicolas Erlijman added a comment - I have re-tested with that branch and the 3-4 sec delay is fixed. Anyway I have 2 comments. 1. Overall performance is slower than 1.7DR2. Also in FF is a bit slower. I test both libraries with same code and 1.7DR2 is faster. 2. Autocomplete in IE is very very slow compared to FF. There is same kind of delay of the menu, when you press some key, there is like 3 secs delay for the div to appear. In FF is much quicker. regards.
              Hide
              Permalink
              Adnan Durrani added a comment -

              Please create a separate JIRA for Autocomplete.

              Show
              Adnan Durrani added a comment - Please create a separate JIRA for Autocomplete.
              Hide
              Permalink
              Adnan Durrani added a comment -

              1.7.1 branch: revision 17172

              Show
              Adnan Durrani added a comment - 1.7.1 branch: revision 17172

                People

                • Assignee:
                  Unassigned
                  Reporter:
                  Nicolas Erlijman
                • Votes:
                  7 Vote for this issue
                  Watchers:
                  1 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: