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

"Hammer-test" suggestions

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

    "Hammer-test" suggestions

    I'm looking for suggestions on how or what to test on an A5 Web app to test performance under stress.

    Background: I recently tested out an Alpha web app by sending it 1000 requests for a 1.5MG PDF file to be emailed back to me. The requests went sequentially, once every 2.5 seconds using HTTP_POST(). The server worked flawlessly and delivered almost all 1000 back in 40 minutes (hence the '2.5 seconds each'). A random five of the emails came back without the PDF, so some timing issue there. It was an exciting 40 minutes for my email client!

    I have a client that needs to know what will happen if X number of users pound on the web app for a particular process (data lookups really).

    Does anyone have experience in this "Hammer technology" and can suggest an appropriate test and what to measure?
    Steve Wood
    See my profile on IADN


    #2
    Re: "Hammer-test" suggestions

    The best way to test your specific application is to simulate actual usage of it. Because every app is different, every app needs to be tested a bit differently. This is of why we haven't said anything like "application x requires a server configured as y" even though many people have requested that type of information.

    There are a number of products available that will let you "record" a web session and then play it back many times over and simulate several users. These range in price from free to many thousands of dollars. Microsoft's Web Application Stress Tool is free and pretty simple to use, but there are better tools available.

    You can also examine your server logs to see exactly how your application is being used in practice. For testing some apps, I have built one-off scripts that use an actual server log as input to generate traffic to a server, even duplicating users' delay between page requests, the exact data submitted, etc.

    Lenny Forziati
    Vice President, Internet Products and Technical Services
    Alpha Software Corporation

    Comment


      #3
      Re: "Hammer-test" suggestions

      That's good stuff, thanks Lenny. I have a log analysis tool and that is a perfect way to mimic, never thought that the log really was an actual set of instructions. Secretly I just want to do this so I can say "Hammer Time" and go in to a crazy dance fever.

      One of the tasks I have here is also to test performance with native DBF versus with an SQL back end. I suspect they will come back with the same results, unless my database tables are huge. I don't suspect that SQL performs better just because there are more concurrent users (if anyone knows, please advise me). I would want to test 10, 25 and 100 concurrent users. I suspect here that, regardless of DBF or SQL, the response time will increase to the point of server lockup at some number.

      Shameless plug - I will be using my new A5-based Internet Task Manager to schedule these runs. iTaskMan - coming soon at www.itaskman.com.
      Steve Wood
      See my profile on IADN

      Comment

      Working...
      X