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

Alpha server consuming large amounts of memory

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

    #16
    Re: Alpha server consuming large amounts of memory

    David is literally one of the ONLY people that contribute to threads asking for help Pete. Pretty sure the forum has been this slow for years, and not because of him.

    Comment


      #17
      Re: Alpha server consuming large amounts of memory

      Well you can see my count is 2,600 odd, no slouch myself, David is very talented and very generous, no denying it, and its appreciated by me as well, there were many talented people as generous in the year past, all I'm saying if something becomes unpleasant to do in a community, people walk or just don't bother... I say that because sometimes that's how I feel, that's all.
      Insanity: doing the same thing over and over again and expecting different results.
      Albert Einstein, (attributed)
      US (German-born) physicist (1879 - 1955)

      Comment


        #18
        Re: Alpha server consuming large amounts of memory

        Thanks Jerry for the great info.

        Somehow I have not used this resource for a long time.

        Simple hello world xbasic a5w-page seems to consume memory about 138 mb.

        Checking this log has to become a routine...

        Kenneth

        Comment


          #19
          Re: Alpha server consuming large amounts of memory

          Check out today's prerelease under bug fixes.
          Mike Brown - Contact Me
          Programmatic Technologies, LLC
          Programmatic-Technologies.com
          Independent Developer & Consultant​​

          Comment


            #20
            Re: Alpha server consuming large amounts of memory

            Thanks for the update, the fact that there is a fix to this issue is a big relief!

            Comment


              #21
              Re: Alpha server consuming large amounts of memory

              Well it's a fix in the pre-release (good) but not the 6012-5338 official release (bad) which is displaying the issue. Be careful going live with a pre-release just to get a fix, caveat emptor.
              Insanity: doing the same thing over and over again and expecting different results.
              Albert Einstein, (attributed)
              US (German-born) physicist (1879 - 1955)

              Comment


                #22
                Re: Alpha server consuming large amounts of memory

                There is no difference between an "official" release and a pre-release. It's just a timing mechanism. One is no better, or worse, than the other.

                An "official" release is simply a release with untested code containing bugs that developers have not yet found.

                A pre-release is a release with untested code and bug fixes developers have found.

                Comment


                  #23
                  Re: Alpha server consuming large amounts of memory

                  Oh dear.. have you ever seen the txt files generated by debugging code in the pre-release. why would they tell you not to use in production, in my view anyone using a pre-release in a live environment is taking full responsibility for the consequences of client liability as by doing so Alpha have no obligation at all. - anyhow choose you own path based on what you now know.
                  Insanity: doing the same thing over and over again and expecting different results.
                  Albert Einstein, (attributed)
                  US (German-born) physicist (1879 - 1955)

                  Comment


                    #24
                    Re: Alpha server consuming large amounts of memory

                    I wish you could know when the next official release is coming out. I'd hate to do a rollback to the previous release (a big to-do at my place) only to have a new official release come out the next day.

                    Performance with the current release is very, very poor compared to the previous release we were running.

                    Comment


                      #25
                      Re: Alpha server consuming large amounts of memory

                      Alpha does not speculate on when the next official release will come out, but maybe we could hope that this particular bug warrants a hotfix?

                      Comment


                        #26
                        Re: Alpha server consuming large amounts of memory

                        Just a comment on version and the Alpha Cloud...

                        If you are running a system for production use, simply follow the advice of Alpha and do not use the pre-release version....EVER. If you have a dev/test setup then you can use the pre-release version no problem. The Alpha Cloud is great for testing out various versions and you can have a dev/test/prod website setup. We have started to publish with the version in the website name until it's ready to go live to it's own url. Example: https://mycoompany-mysitename-dev.cl...ware.com/6012/

                        Comment


                          #27
                          I started receiving an error "not enough spare threads" that seems to date back in my logs to Sept 27. Not sure what I did that day. Anyway, I just turned on Raw HTTP log. I read what Jerry posted earlier, and I see what I should compare, but I don't really know what some stuff means such as Sessions/Tables/Variables/Exceptions|Memory/Peak/PageFaults: 11/2/4033/0|142848000/180813824/187133. Some of my lines show (Orphans) after the last number. I thought Page Faults was a bad thing, no? Should I be looking for exceptions > 0? Is there a link between the time of the thread error in my access log and the time in the raw HTTP? I'm looking in both, and I'm not seeing an obvious link such as the time difference that Jerry referenced. I guess i need an education on what stuff means in the log.

                          Comment


                            #28
                            Why not send the logs to Alpha and have them process them and find out.
                            Insanity: doing the same thing over and over again and expecting different results.
                            Albert Einstein, (attributed)
                            US (German-born) physicist (1879 - 1955)

                            Comment


                              #29
                              Pete, Reply #2 from Selwyn encouraged figuring out which component or page as the leak. Jerry's reply discussed how to find out. They no longer have a tool to do this. If i understand how it works and what it means, I can make my own tool and address it every time it happens beyond just this one time. Plus, if they don't see the problem in the piece I send them, the ball is back in my court anyway. That's why I'm looking to figure it out. Maybe it'll work for me, and maybe it won't.

                              Comment


                                #30
                                I'd just go back to the working build and wait for the fix - It maybe its not be your bad. - I went through this years ago - I can tell you one thing doing timer event refreshes was a big problem at the time - anyhow good luck with it.
                                Insanity: doing the same thing over and over again and expecting different results.
                                Albert Einstein, (attributed)
                                US (German-born) physicist (1879 - 1955)

                                Comment

                                Working...
                                X