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

WAS Update from version 2549 to 2736 unbelievable results

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

    WAS Update from version 2549 to 2736 unbelievable results

    I did update to my developer version 11 from build 2549 to 2736. Server is a cloud server in Leaseweb cloud.

    In stress test the Was performance is about 10-12 times better than before. When you continue stress over 30 seconds Was also handles this situation much more better than before (10-12 times) and it also recovers situation and don't drop almost anything. This is a big contrast to the build 2549.

    In version 2549 the cpu usage was all the time between 10-40%(never figured out why). Now in build 2736 when no traffic the usage is 0% as is it should.

    Unbelievable good results. No dark clouds anymore.

    #2
    Re: WAS Update from version 2549 to 2736 unbelievable results

    Do you think the latest build 2734 is stable enough to by used in production?

    Comment


      #3
      Re: WAS Update from version 2549 to 2736 unbelievable results

      Originally posted by gaby_h View Post
      Do you think the latest build 2734 is stable enough to by used in production?
      See the pre-release notes advice "Not for production" use at your own risk. But i read a comment from Richard Rabins on linkedin.com Alphagroup perhaps in two weeks, but is not a final promise.

      Comment


        #4
        Re: WAS Update from version 2549 to 2736 unbelievable results

        I have always wondered how WAS workers actually work. In version 10 (default settings) when server start there is 4 workers but in practice WAS right a way thought it needs 4 more(although there was 3 workers still available) . After this it also did keep all spare workers it got.

        In version 11 (default settings) we start right a way with 8 (+2) workers and if WAS needs more it is already in condition when response time is quit long or WAS begins to drop requests. My conclusion is that if WAS thinks it needs more than 8 + 2 workers then performance has already dropped because of heavy load and the extra workers in fact do not help at all anymore.

        Comment


          #5
          Re: WAS Update from version 2549 to 2736 unbelievable results

          Thanks for the update Ken.... I too am very anxious for this new release to go live as I'm sure many others are as well. In my case I've been mostly interested in the bug/performance fixes

          Comment


            #6
            Re: WAS Update from version 2549 to 2736 unbelievable results

            Originally posted by ids-dave View Post
            Thanks for the update Ken.... I too am very anxious for this new release to go live as I'm sure many others are as well. In my case I've been mostly interested in the bug/performance fixes
            This thread is just for performance. I am very happy to the difference in performance between these builds as I pointed out in my first post.

            But as I also pointed out in my second post there is a bottleneck: if you don't get more workers then you can forgot better performance. Better server more memory don't help at all. The biggest amount of workers I have succeed to get is 14 and but as I pointed out performance drops already if you need more than 10 workers. But my testing is quit limited.

            Comment

            Working...
            X