Alpha Software Mobile Development Tools:   Alpha Anywhere    |   Alpha TransForm subscribe to our YouTube Channel  Follow Us on LinkedIn  Follow Us on Twitter  Follow Us on Facebook

Announcement

Collapse

The Alpha Software Forum Participation Guidelines

The Alpha Software Forum is a free forum created for Alpha Software Developer Community to ask for help, exchange ideas, and share solutions. Alpha Software strives to create an environment where all members of the community can feel safe to participate. In order to ensure the Alpha Software Forum is a place where all feel welcome, forum participants are expected to behave as follows:
  • Be professional in your conduct
  • Be kind to others
  • Be constructive when giving feedback
  • Be open to new ideas and suggestions
  • Stay on topic


Be sure all comments and threads you post are respectful. Posts that contain any of the following content will be considered a violation of your agreement as a member of the Alpha Software Forum Community and will be moderated:
  • Spam.
  • Vulgar language.
  • Quotes from private conversations without permission, including pricing and other sales related discussions.
  • Personal attacks, insults, or subtle put-downs.
  • Harassment, bullying, threatening, mocking, shaming, or deriding anyone.
  • Sexist, racist, homophobic, transphobic, ableist, or otherwise discriminatory jokes and language.
  • Sexually explicit or violent material, links, or language.
  • Pirated, hacked, or copyright-infringing material.
  • Encouraging of others to engage in the above behaviors.


If a thread or post is found to contain any of the content outlined above, a moderator may choose to take one of the following actions:
  • Remove the Post or Thread - the content is removed from the forum.
  • Place the User in Moderation - all posts and new threads must be approved by a moderator before they are posted.
  • Temporarily Ban the User - user is banned from forum for a period of time.
  • Permanently Ban the User - user is permanently banned from the forum.


Moderators may also rename posts and threads if they are too generic or do not property reflect the content.

Moderators may move threads if they have been posted in the incorrect forum.

Threads/Posts questioning specific moderator decisions or actions (such as "why was a user banned?") are not allowed and will be removed.

The owners of Alpha Software Corporation (Forum Owner) reserve the right to remove, edit, move, or close any thread for any reason; or ban any forum member without notice, reason, or explanation.

Community members are encouraged to click the "Report Post" icon in the lower left of a given post if they feel the post is in violation of the rules. This will alert the Moderators to take a look.

Alpha Software Corporation may amend the guidelines from time to time and may also vary the procedures it sets out where appropriate in a particular case. Your agreement to comply with the guidelines will be deemed agreement to any changes to it.



Bonus TIPS for Successful Posting

Try a Search First
It is highly recommended that a Search be done on your topic before posting, as many questions have been answered in prior posts. As with any search engine, the shorter the search term, the more "hits" will be returned, but the more specific the search term is, the greater the relevance of those "hits". Searching for "table" might well return every message on the board while "tablesum" would greatly restrict the number of messages returned.

When you do post
First, make sure you are posting your question in the correct forum. For example, if you post an issue regarding Desktop applications on the Mobile & Browser Applications board , not only will your question not be seen by the appropriate audience, it may also be removed or relocated.

The more detail you provide about your problem or question, the more likely someone is to understand your request and be able to help. A sample database with a minimum of records (and its support files, zipped together) will make it much easier to diagnose issues with your application. Screen shots of error messages are especially helpful.

When explaining how to reproduce your problem, please be as detailed as possible. Describe every step, click-by-click and keypress-by-keypress. Otherwise when others try to duplicate your problem, they may do something slightly different and end up with different results.

A note about attachments
You may only attach one file to each message. Attachment file size is limited to 2MB. If you need to include several files, you may do so by zipping them into a single archive.

If you forgot to attach your files to your post, please do NOT create a new thread. Instead, reply to your original message and attach the file there.

When attaching screen shots, it is best to attach an image file (.BMP, .JPG, .GIF, .PNG, etc.) or a zip file of several images, as opposed to a Word document containing the screen shots. Because Word documents are prone to viruses, many message board users will not open your Word file, therefore limiting their ability to help you.

Similarly, if you are uploading a zipped archive, you should simply create a .ZIP file and not a self-extracting .EXE as many users will not run your EXE file.
See more
See less

Component Size and speed

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Component Size and speed

    Are there any recommended ways to increase the speed of components?

    I have a large component which consists of a few embedded grids and list boxes. These are live links, but I think the main problem is the size rather than the links to the database - this particular component is almost 500kb.

    I've tried setting the load option of the embedded grids to button click, rather than when page is loaded, but this doesn't seem to make a difference.

    Is there a way to compress component size? It takes almost 12 seconds to load. The client is very happy with the layout of the controls, so I'm trying to find a solution which wouldn't involve changing the overall layout of the component.

    It is a MySQL backend, but doing changes there doesn't help. Creating a new ux with only one list box which is based on a pretty complex query still loads within 2 seconds. This is why I think its the size of the UX itself rather than the queries, links etc that is causing the problem.

    Any help appreciated

  • #2
    Re: Component Size and speed

    Originally posted by jrmplus View Post
    Are there any recommended ways to increase the speed of components?

    I have a large component which consists of a few embedded grids and list boxes. These are live links, but I think the main problem is the size rather than the links to the database - this particular component is almost 500kb.

    I've tried setting the load option of the embedded grids to button click, rather than when page is loaded, but this doesn't seem to make a difference.

    Is there a way to compress component size? It takes almost 12 seconds to load. The client is very happy with the layout of the controls, so I'm trying to find a solution which wouldn't involve changing the overall layout of the component.

    It is a MySQL backend, but doing changes there doesn't help. Creating a new ux with only one list box which is based on a pretty complex query still loads within 2 seconds. This is why I think its the size of the UX itself rather than the queries, links etc that is causing the problem.

    Any help appreciated
    Are you loading everything at once? If yes, try to open only as needed.

    Have you tried not pre-populating grids until they do a search?

    Comment


    • #3
      Re: Component Size and speed

      All the embedded grids and list boxes need to be loaded more or less straight away. I'm using a tab control with each embedded grid in its own tab pane.

      There aren't any images or other files linked to the component - its all text controls, check boxes, grids, etc.

      Comment


      • #4
        Re: Component Size and speed

        Originally posted by jrmplus View Post
        All the embedded grids and list boxes need to be loaded more or less straight away. I'm using a tab control with each embedded grid in its own tab pane.

        There aren't any images or other files linked to the component - its all text controls, check boxes, grids, etc.
        Technically not true, you could perhaps make it so they get loaded when the Tab is clicked. Have you thought about using Panels instead?

        Comment


        • #5
          Re: Component Size and speed

          I've tried changing the show mode of the embedded grids to 'when button is clicked' rather than 'When page is loaded' but that doesn't help at all. I assume the component has already been loaded by this stage anyhow - this only relates to show/hide option?

          What I meant in previous post was that most of the information contained in the grids/listboxes, etc needs to be visible on screen for the user. Being able to view a large amount of data at one time is what the client needs.

          Comment


          • #6
            Re: Component Size and speed

            You said your MySQL is based on a query, as opposed to a view.
            • Can you provide some detail on the query, such as, how many joins/tables are involved?
            • How many rows are returned typically?
            • Are you performing lots of calculations for "virtual" columns?
            • Is the grid editable?

            As an aside, Lists are much more efficient than grids. Selwyn's words, not mine.

            Comment


            • #7
              Re: Component Size and speed

              Off the track just a bit, but maybe worth asking for your benefit.

              What server are you on? How truly fast is it??

              I load 20+ of my own sites per day and have a few that are inherently slow compared to the same on a different server. 500kb does not sound extremely large to me, although it would load a bit slower than 50kb.
              Dave Mason
              [email protected]
              Skype is dave.mason46

              Comment


              • #8
                Re: Component Size and speed

                Originally posted by westridge View Post
                You said your MySQL is based on a query, as opposed to a view.
                • Can you provide some detail on the query, such as, how many joins/tables are involved?
                • How many rows are returned typically?
                • Are you performing lots of calculations for "virtual" columns?
                • Is the grid editable?

                As an aside, Lists are much more efficient than grids. Selwyn's words, not mine.

                It doesn't seem to be the tables or queries which are slowing things down. In my earlier post, I mentioned that in order to test this, I created a new ux component with a single list box based on quite a complex query and the whole component loaded quite quickly.
                I have tried using views as well as limiting rows, etc but it doesn't make any difference to load speed. The queries which the embedded grids are based on are quite straightforward - 2 or 3 tables at most. The number of rows returned is also small and any calculated columns are quite limited.

                Comment


                • #9
                  Re: Component Size and speed

                  Originally posted by DaveM View Post
                  Off the track just a bit, but maybe worth asking for your benefit.

                  What server are you on? How truly fast is it??

                  I load 20+ of my own sites per day and have a few that are inherently slow compared to the same on a different server. 500kb does not sound extremely large to me, although it would load a bit slower than 50kb.

                  It's a windows 2008 server 64-bit with 12 GB RAM.

                  There isn't any speed issue elsewhere - there are a few other sites running on this server as well.

                  I'll take a look at using lists instead of grids to see if that helps.

                  Comment


                  • #10
                    Re: Component Size and speed

                    Have you looked at each individual control, form the standpoint that one maybe slowing the load down? Any are any pulling data not needed right away? Maybe limit them to smaller views.
                    Nicholas Wieland
                    LedgerSuite.com Corp
                    [email protected]
                    http://www.ledgersuite.com

                    Comment


                    • #11
                      Re: Component Size and speed

                      Re few embedded grids and list boxes how many is a few - re: I'll take a look at using lists instead of grids to see if that helps. - are they lists or drop-downs? - be more specific - show examples.
                      Insanity: doing the same thing over and over again and expecting different results.
                      Albert Einstein, (attributed)
                      US (German-born) physicist (1879 - 1955)

                      Comment


                      • #12
                        Re: Component Size and speed

                        I've just tried opening the UX as a window rather than a TabbedUI and it opens much quicker.

                        Opening as a window takes less than 2 seconds, whereas a tabbedUI takes about 12 seconds. The first time the windows opens however, it takes slightly longer, but that isn't a big deal. Does opening as a window save a cached version somehow? When the window is closed, is it really only hiding it? When opening the tabbedUI, I have checked the option 'use cached UX component' but it still takes 12 seconds to open every time.

                        If closing the TabbedUI was actually hiding it - the same as seems to be happening with the window - that would be an ideal solution.

                        Anyway - I can work with the window option for now - certainly a big improvement.

                        Comment

                        Working...
                        X