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

Thread was busy 99% of the last 20 seconds

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

  • Thread was busy 99% of the last 20 seconds

    We have a button that does an AJAX callback and selects rows from our database and loops through them to create a CSV.
    The select statement can return a varied 10k-50k rows - because of that it seems the application server gets hung up which causes
    a site-wide slowdown (as illustrated in the log below).


    Are there any settings I can tweak to have this functionality behave without affecting the rest of the site? I know that it may be long-running..but I need it to complete.
    If the Alpha Web Server does not work - is there any other approach/workaround I can take to have this behave appropriately?

    Thanks in Advance

    Here is my XBASIC Stack Log
    Tue Jul 04 15:28:18 2017


    Thread: AppServerWorker6
    Request URI: /app/__a5RunDialog.a5w?__pageName=AAProcessPayroll.a5w&__dialogFilename=uxProcessPayroll&__alias=UXPROCESSP&__unsaved=no
    Line: 351 else
    Thread priority reduced.
    Thread was busy 99% of the last 20 seconds.
    Raw Data: {not sure what this represents, omitted for privacy}
    The script causing this behavior is using a lot of CPU time.
    You may want to review the page to make sure you have optimized any XBasic scripting.

    Long running and processor intensive scripts tend to tie up available threads and adversely affect the perceived performance for multiple users.


    Execution Stack:
    0#1 evaluate_shared_private(
    0#37 OOhttpdServerClientMIME(ptemp,"AppServerMain")
    0#2 A5WCallResult = evaluate_a5w_to_response(page_contents,Response,quote(" " + eval_settings.global.Request.ScriptName),eval_settings,EVALUATE_A5W_TIMEOUT,RequestBundle.RequestInfo.Filename.Path)
    0#179 x_out = a5_ajax_dialog2(tmpl)
    0#351
    Scott Moniz - Computer Programmer/Analyst
    REA Inc.
    http://reainc.net
    (416)-533-3777
    [email protected]

    REA INC offers consulting services, programming services, systems design, database design, third party payment gateway integration (CHASE, PAYPAL, AUTHORIZE.NET) and developer support.
    If you need custom code, or 1-to-1 mentoring in any facet of your database/web application design,
    contact us to discuss options.

  • #2
    Re: Thread was busy 99% of the last 20 seconds

    Scott- can you do this as a SQL stored procedure?

    Another option that may or may not fit your needs is to set up a separate runtime instance to do this as needed. One side benefit might be that other similar tasks can also be offloaded to the runtime.
    -Steve
    sigpic

    Comment


    • #3
      Re: Thread was busy 99% of the last 20 seconds

      Scott,
      Another idea would be to break it into two steps. Make the 10K to 50K table a temporary table (In MariaDB I'd use a memory engine table), then release the main table and do your export to CSV from the smaller temp table.
      Pat Bremkamp
      MindKicks Consulting

      Comment


      • #4
        Re: Thread was busy 99% of the last 20 seconds

        We are using SQL server which does not have an INTO OUTFILE like MySQL so we cannot export directly from a table/query to a file. With Alpha WAS acting as the middleman for the CSV generation it seems the large recordset is not playing nicely.

        One approach we are going to explore is using a SQL Server stored procedure as Steve suggested and using cmdshell in order to use the bcp.exe utility outlined here for file generation:
        https://docs.microsoft.com/en-us/sql/tools/bcp-utility

        Hopefully this does work, but if not I think offloading the process to another instance (possibly even PHP+Apache if performance merits) is going to be the Plan B.

        Will report my results in case it helps anyone in the future.

        Appreciate your time / input Steve and Pat.
        Last edited by aburningflame; 07-05-2017, 12:45 PM.
        Scott Moniz - Computer Programmer/Analyst
        REA Inc.
        http://reainc.net
        (416)-533-3777
        [email protected]

        REA INC offers consulting services, programming services, systems design, database design, third party payment gateway integration (CHASE, PAYPAL, AUTHORIZE.NET) and developer support.
        If you need custom code, or 1-to-1 mentoring in any facet of your database/web application design,
        contact us to discuss options.

        Comment


        • #5
          Re: Thread was busy 99% of the last 20 seconds

          Setting up a runtime instance is easy, requires very little resources, and just sits there and does the job very nicely. I'm constantly working to shove more and more off to runtime in my biggest application. It just fires a function every 60 seconds that checks, then processes whatever is in the work queue.

          The most complex part of it is building a work queue processor, but it's not that hard and, of course, its reusable.
          -Steve
          sigpic

          Comment


          • #6
            Re: Thread was busy 99% of the last 20 seconds

            Steve, is the runtime setup on the same machine as WAS? To piggyback off that question is there any documentation on how to setup multiple runtime processes on the same machine?

            Comment


            • #7
              Re: Thread was busy 99% of the last 20 seconds

              Originally posted by Steve Workings View Post
              Setting up a runtime instance is easy, requires very little resources, and just sits there and does the job very nicely. I'm constantly working to shove more and more off to runtime in my biggest application. It just fires a function every 60 seconds that checks, then processes whatever is in the work queue.

              The most complex part of it is building a work queue processor, but it's not that hard and, of course, its reusable.
              This is an amazing idea.

              I have not used runtime lately but I can see the benefits.

              Runtime also has nodejs integration so you can start for example separate(s) Expressjs server(s) from runtime to show results or to take form inputs from user and so on (I have not yet tested this). Possibilitys are endless using runtime and its nodejs integration. You can operate together with Was or without it.

              Comment


              • #8
                Re: Thread was busy 99% of the last 20 seconds

                Originally posted by kkfin View Post
                This is an amazing idea.

                I have not used runtime lately but I can see the benefits.

                Runtime also has nodejs integration so you can start for example separate(s) Expressjs server(s) from runtime to show results or to take form inputs from user and so on (I have not yet tested this). Possibilitys are endless using runtime and its nodejs integration. You can operate together with Was or without it.
                Exactly! I'm assuming a few runtime instances installed into different locations, monitored by always up, talking to the database as well as a cluster of expressjs servers will allow an app to increase concurrent users without additional WAS licenses. My employer moved on from Alpha, even though they could afford a hundred annual licenses, because of WAS unreliability. Now using Google Firebase for $25/mo gives them 100,000 concurrent user limit on the db plus all the other free cloud functions...and it is *always up*.

                Comment


                • #9
                  Re: Thread was busy 99% of the last 20 seconds

                  Scott, we had the same type thing going on a few years ago with 100K record batches. The database stored procedure to an indexed staging table solution removed the WAS processor load and allowed the user to issue the callback, wait a bit for success response, then click the "export to excel" button which hit the staging table.

                  Comment

                  Working...
                  X