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
Devcon 2020 Goes Virtual! LEARN MORE >

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

IIS Slow startup

Collapse
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
    #1

    IIS Slow startup

    Hi All,

    I'm migrating a site from the WAS to IIS and I'm beginning to regret my decision

    the target is iis 8.5. on standard server 2012, r2 8gig memory and 4 cores.
    alpha is version 12.0.5221.0

    The website uses a tabbedUI to navigate around the app. The display of all the components within it (about 30) is controlled by roles and alpha web security.

    On WAS this works like a charm, and has done so, with perfectly respectable response times, for over 3 years.

    On IIS, any activity after an idle (approx 30 minutes or overnight) period can take over 20 seconds to display the application in the browser.
    The initial login page is fine, the app loads the security information of the user, the tabbedUI is then displayed. The tabbedUI is usually left on screen

    Once this has displayed, performance is fine, until there has been a idle period (again 20-30 minutes). Other users can log in and use the site and the performance is fine.
    It seems while the site is active performance is fine.


    So far I have I checked everything in the web about IIS slow startup
    1. enable application preload is checked
    2. session lifetime for the project is set for 600 minutes
    3. checked load on startmode is 'ALWAYSRUNNING'
    4. turned off the idle time delete so nothing is discarded
    5. increased the grid cache size to 100mb
    6. ensured the required IIS modules (ApplicationInitializationModule) are installed to make these options work



    has anybody got ideas about
    1. any other parameters I can look at?
    2. had similar problems (and solved them)?
    3. My experience with debugging websites uses chrome or firebug is pretty limited, is there a way I can see where the time is actually going?



    cheers
    Garth
    Tags: None
    #2
    Re: IIS Slow startup

    Hi All,

    just a little followup... this seemed to be an issue with the way I'd set up the IIS binding. I'd used both hostname and IP address, it seems our firewalls were getting confused as to how IIS was responding
    to requests. The apparent timeout aspect was most likely due to the firewalls timing out what they thought were orphaned connections...

    I hate firewalls... !!!

    Garth

    Comment

      #3
      Re: IIS Slow startup

      I thought this might be the case for one of my customers under traditional WAS that connected to our hosting server. This one customer kept reporting "timeout" problems, while other customers did not. Wondering if it might be their firewalls changing the contents of the message packets and confusing our host load balancer, I installed a timer event into the UX that displays on the tabbedUI "Home Page". The timer fires an ajax callback about every two minutes. The xbasic for the callback records the time of the message to my supplementary user table and sends back a response - the server's current date/time. I have not proved this fixed the problem, though. But I have not had any more complaints. Also, shortly after that, I upgraded to a faster server with more RAM and split the SQL database out to a separate server and also removed the load balancer. As far as I know the server is also running without AlwaysUp and it has only failed once in the last couple of months and that was when I tried to "publish" to it. I'm in process of moving this to AA IIS.

      p.s. In the move to IIS I have also switched to development testing under Edge (instead of Chrome) and I have noticed Edge is usually sluggish. Sometimes, it starts out okay, but after being in the system for just a few minutes it slows down. I don't think it is necessarily the fault of AA IIS. I'm beginning to suspect the JS library is doing things that Edge cannot handle very well, since sometimes Edge behaves fine. Other developers have been confirming they recommend Chrome over Edge due to speed.

      Comment

      Previous template Next
      Working...
      X