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



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

Diagnosing a slow server?

  • Filter
  • Time
  • Show
Clear All
new posts

  • CharlesParker
    Re: Diagnosing a slow server?

    As I just pointed out in another thread you can watch page load times in goggle chromes dev tools. I have found that an outdated google map api will cause major lag as a for instance - even though I was no longer using the mapping part of my component, the UX was still loading the files. Good luck, if you find something that is more of an Alpha thing and less of a particular component thing please let us know what we can do to avoid it!

    Leave a comment:

  • mikeallenbrown
    Re: Diagnosing a slow server?

    The app server has server logging functions you could turn on. You may be able to track down the source after examining the logs.

    Leave a comment:

  • GP-FBD
    Re: Diagnosing a slow server?

    I have seen the threads about running multiple instances, but that's not a solution. There is some web component which is causing alpha five to choke on itself. Running more instances will simply give A5 more chances to choke.

    I'm specifically looking at attempting to profile where alpha five spends most of its time executing to see if there is some component or report which is taking up most of the resources. I see that A5 does have some support for profiling, but the profiler needs to run within some x-basic code. This A5 application was built entirely out of the standard grid templates & reports so I'm not sure where the profiling code could be stuck.

    Leave a comment:

  • mikeallenbrown
    Re: Diagnosing a slow server?

    You can run more than one instance of the app server ... do a forum search. There is a well documented thread on that here. Sorry, I'm about to leave and couldn't search myself. We use two app servers (six intances, three instances per server) and a load balancer to spread users out. Also, we restart the server nightly.

    Leave a comment:

  • GP-FBD
    started a topic Diagnosing a slow server?

    Diagnosing a slow server?


    We are running an alpha five server (2999-4519) and it has been extremely slow lately. We have about 20-30 simultaneous users using about 450 web components and 80 reports. The alpha five server is rebooted weekly, but a few days after a reboot it grinds to a halt with page loads taking up to 30s. The whole business runs on the alpha five server so it's obviously not ideal for it to.. you know.. not work.

    Anyway, is there any sort of performance console hidden away somewhere so that I can see where Alpha Five spends most of its time? I want to know if this is an issue with the queries, the database, or with A5 itself somehow.