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

Developer "SAVE" very slow. Same for LIVE or WORK Preview.

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

    Developer "SAVE" very slow. Same for LIVE or WORK Preview.

    Powerful PC. Win-10-Pro. 48 cores (yeah, 48.) 64gig RAM (yeah, 64.) No virtual network installed.

    SAVE on modest Grid or UX components is taking 20-30-40 seconds. A minute or two.

    Not seeing network activity, not seeing disk hits, not even seeing a CPU spike.

    Build 6012_5338.

    Taking 3/4/5 times as long to save to SSD drives < 6 months old.

    It's hurting my productivity.

    Version.jpg
    Carl ~ Dallas, TX
    I'm so old that pool balls came with Roman Numerals

    #2
    Re: Developer &quot;SAVE&quot; very slow. Same for LIVE or WORK Preview.

    Is the database indexed etc? Is it a single key or multiple keys? How many columns?

    Comment


      #3
      Re: Developer &quot;SAVE&quot; very slow. Same for LIVE or WORK Preview.

      SQL. Two test rows. Highly indexed. Even the SAVE is taking forever and that is all local.

      Only started with the last couple of updates. However I do see a single CPU hard spike that coincides with the long delay.

      I also see more Ethernet activity that I first discovered. Trivial, and I doubt it is related.

      See attached Task Manager image. It's a fairly simple grid.

      SAVE.jpg
      Last edited by CarlMPearson; 08-13-2019, 01:56 PM.
      Carl ~ Dallas, TX
      I'm so old that pool balls came with Roman Numerals

      Comment


        #4
        Re: Developer &quot;SAVE&quot; very slow. Same for LIVE or WORK Preview.

        If I recall correctly, there's been one or two posts recently about i/o between Alpha and the SQL backend becoming slow. I wonder if the recent versions of the AlphaAnywhere installer have been installing different DLL's for communicating with SQL or AA is choosing to communicate with SQL using different protocols than it did previously. In the past, one of the solutions for compatibility problems between Alpha and SQL was to install the Microsoft SQL Server Native Client after installing/updating AlphaAnywhere.

        https://docs.microsoft.com/en-us/sql...ql-server-2017

        Here's some older info on SQL protocols:
        https://docs.microsoft.com/en-us/sql...ql-server-2014

        Comment


          #5
          Re: Developer &quot;SAVE&quot; very slow. Same for LIVE or WORK Preview.

          Is it hitting the SQL server for a GRID SAVE in development?

          I'd guess most of us try to Work-Save-Work-Save-Work-Save-Work-Save-TEST

          Those 25 second saves are getting painful.
          Carl ~ Dallas, TX
          I'm so old that pool balls came with Roman Numerals

          Comment


            #6
            Re: Developer &quot;SAVE&quot; very slow. Same for LIVE or WORK Preview.

            I would not be surprised if the IDE fetches column information from SQL when you save a component. I recall doing something in the IDE and AA wanted access to SQL at a time when I thought it should already have everything it needed about column information from the properties in the component.

            The are other reasons why saving a component may have slowed down:

            1) There might be an excessive amount of automatic backup copies of your component(s).
            To locate your auto backup folder, do the following from your "Web Projects Control Panel" window:
            - Click "Project Properties" button.
            - Click "Design-time Properties" tab.
            - The "Backup folder" will be listed first. Take a look at its contents in File Explorer.
            - There is a checkbox option to remove old backups along with configuration parameters for it. I've never used this option, though. I just let the backups accumulate until I update AA versions, at which point I start over with new project and backup folders. Although, I hate loosing my publishing profiles for each new project folder I create. (I need to see if the Web Projects Control Panel / "File / Clone workspace" option preserves publishing profiles. )

            2) You may have backup software running that is attempting to backup the folder(s) that Alpha use for its component backups and project files. I would exclude these from live backups and just include the daily workspace backup folder in any live backup that you are running. To find the daily backup folder:
            a) Open the "Control Panel" (not the Web Projects one)
            b) From main menu select "Tools" / "Backup Restore Workspace" / "Backup workspace"
            c) The backup folder is display near the top.

            3) The Windows TEMP folder might be full - make sure you have emptied that.

            P.S. If you set your component and workspace backup folder to be specifically outside of your Project folder, such they include absolute paths, then always be sure to update / change them if you copy or clone your project!
            Last edited by RichCPT; 08-13-2019, 05:47 PM. Reason: added # 3

            Comment


              #7
              Re: Developer &quot;SAVE&quot; very slow. Same for LIVE or WORK Preview.

              I've run into similar issues when developing on a Windows 10 machine.

              Try doing the following:
              Click the Windows start button
              Right click the Alpha Anywhere icon and click on more
              Then click on Run as Administrator
              Manually point to your project and load it

              Even though you can set the app to always run in administrator mode when the icon is clicked, it seems to ignore it unless you do it as above.

              Comment

              Working...
              X