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

Can maxed-out web server CPU really handle more instances of Alpha

  • Filter
  • Time
  • Show
Clear All
new posts

  • Can maxed-out web server CPU really handle more instances of Alpha

    So, I am really having a hard time believing that a web server that has a maxed-out CPU, based on the steady 100% CPU utilization shown by Windows Performance Monitor, could actually handle more instances of Alpha under IIS or traditional AA WAS.

    What am I missing here, how can the Windows Performance Monitor be so wrong that it would actually work to put more running instances of IIS or WAS on the system?

    When I stress test my app, each of the four CPU cores shows 100% usage in the graph. I estimate the CPU cores can handle about 5 users at a time, and even at that small number, performance is not very good. (These are "busy" users - requesting new ~20 record Grid pages every couple of seconds.)

  • #2
    Re: Can maxed-out web server CPU really handle more instances of Alpha

    Rich - something doesn't sound right. And as I'm sure you know, there are a lot of factors.

    Are you sure all that CPU usage is really from your app? What does it look like when you don't have the app running at all? And then when you start your app and users start using it, can you attribute the growing consumption to that activity?

    I've seen one popular malware package and other pieces of Windows consume a whole lot of CPU.

    And, how much RAM do you have?


    • #3
      Re: Can maxed-out web server CPU really handle more instances of Alpha

      6GB RAM.
      SQL Server is on another server and its CPU usage is quite low.
      I ran the load test twice and yes, the CPU usage is low on the Web Server until the cloud-based load testing servers spin up and start adding users to the system.
      I had all regular users off of the system and the web-site that services them had been disabled in IIS, so only the load testing web site was running in IIS.


      • #4
        Re: Can maxed-out web server CPU really handle more instances of Alpha

        You're plenty experienced so I have confidence your app is well-designed, etc. But after some thought, I wonder if it's worth some review.

        Grids of course are not as good as some of the newer controls. But before anything too deep, I wonder if you could load test it against some extremely simple page. Or, make a very simple page with a list showing the same data, and test against that.

        And, if your app is dependent on continuous and new retrievals of records like this, it's probably wise to consider lists or viewboxes as substitutes anyway for best performance.


        • #5
          Re: Can maxed-out web server CPU really handle more instances of Alpha

          Rich, you are assuming your app is what causing the issue, every time I've seen this, it is a result of outside attacks on the alpha server being hit sometimes 100's of times a second, these are mainly from china you may need to add software to manage these attacks, as it causes a denial of service like what you are experiencing. RDPGuard will help you verify and resolve it.

          Hope this helps.
          Insanity: doing the same thing over and over again and expecting different results.
          Albert Einstein, (attributed)
          US (German-born) physicist (1879 - 1955)


          • #6
            Re: Can maxed-out web server CPU really handle more instances of Alpha

            Any continouos server side workflow (or simililar situation) will in practise immediately kill Alpha server. You can test this with most simple loop. This is good to remember.


            • #7
              Re: Can maxed-out web server CPU really handle more instances of Alpha

              Steve Workings,
              Yes there are a chain of three Grids in this test scenario. The 3rd Grid (the one opened and closed 10 times in the load script) is easily replaced with a UX with a LIST. I am recoding the test script to work under a different testing platform and I will have it open the UX version on that 3rd step. I had done the test with a Grid in the third step as I had created that Grid to run faster than the UX. On my Dev computer I observed a simplified Grid had a much smaller payload than the UX and the Grid seemed to load faster on my Dev computer than the UX. But the time savings I saw on my Dev computer did not translate to any savings on the Server.

              Do you mean if I am doing my own xbasic processing or are you saying that just the stuff Alpha does to process a Grid will overwhelm the server?

              Yes, I suppose the server could be busy trying to handle bogus requests that I don't know about. But the CPU usage does start out quite low and only gets pegged when the load test users come online. I will see if IIS has a log of requests I can look at.


              • #8
                Re: Can maxed-out web server CPU really handle more instances of Alpha

                Just saying.
                Insanity: doing the same thing over and over again and expecting different results.
                Albert Einstein, (attributed)
                US (German-born) physicist (1879 - 1955)


                • #9
                  Re: Can maxed-out web server CPU really handle more instances of Alpha

                  For WAS. There is two things that has direct impact for performance here. First is Application Server and other is code running in server.

                  Application server uses server threads to balance traffic. Normally there are 8 available at start and 4 for spare. These are quick and lack is slow. But if more is needed then to activate more threads takes little time which has direct impact for performance. Normally 48 threads is maximum. Then you have to wait for one task to get finished to get a free thread. So basically after 12 things get little slower and very soon very slow.

                  Application server running in 64 bit Windows can consume 2 GB memory but maybe the real limit is 1GB and then Application server is already far from responsive. The question is anymore who will switch the lights off.

                  What comes to code in server some xbasic code can be running simultaneously some not. This is the reason why for example a simple loop can kill whole server. Also note. Most simple UX/Grid is a quite punch of code. If many loads it same time the size of module has direct impact to performance.

                  By the way. There is an easy xbasic function A5W_AnalyzeWebAccessLogs() you can use to check access logs using a web page. I have find that it do not work with reverse proxy at least with my current combination. I get some ajax errors.


                  • #10
                    Re: Can maxed-out web server CPU really handle more instances of Alpha

                    Keep pushing Rich.
                    Very interested in this thread