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 Edition - Build 3608 - CPU at 100%

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

    Developer Edition - Build 3608 - CPU at 100%

    My development machine is Win7 Ultimate, 8-core, 11-gig.

    SAVE of a grid used to be a mere blip but now takes 10-15 seconds. That sent me looking to see what might be slowing down matters.

    When I have any grid open in Design mode, my CORE-1 pins at 100%. Close the grid, and it drops to nil. Other CORE percentages settle down, but Core-1 goes solid.

    It only seems to pin the meter when ACTION BUTTONS are in play on the grid. On grids without Action Buttons, it acts normal.

    That might be a misleading clue but the 100% CPU meter and the 10-15 second SAVE operation is consistent.
    Last edited by CarlMPearson; 10-25-2010, 04:22 PM.
    Carl ~ Dallas, TX
    I'm so old that pool balls came with Roman Numerals

    #2
    Re: Developer Edition - Build 3608 - CPU at 100%

    Local or remote DB backend?
    MYSQL/SQLSERVER/Access?
    Your OS version makes no difference Home or Ultimate to A5
    I am working on a dev machine I7 4GB no problems with action buttons to a remote backend DB

    Comment


      #3
      Re: Developer Edition - Build 3608 - CPU at 100%

      Remote. SQL Server 2008.

      No problem with most grids. Saving locally. No problem loading the grid, it comes up quick.

      A 3ghz CPU at 100% is not good. It does not settle down. It stays pinned.

      It may not be the Action Buttons, but it is the only clue I have spotted.
      Carl ~ Dallas, TX
      I'm so old that pool balls came with Roman Numerals

      Comment


        #4
        Re: Developer Edition - Build 3608 - CPU at 100%

        I always notis very long saving times of grids (against local, mysql backend) if the table which is used by the grid is rather large (say more than 100.000 records).
        Ger Kurvers
        Alpha Anywhere / V4.6.1.9- Build 6488 (production) / V4.6.5.1 - 8722-5683(testing)
        Development: Mysql, windows 10 64 Applicationserver: standard on Windows server 2019

        Comment


          #5
          Re: Developer Edition - Build 3608 - CPU at 100%

          I have also noticed with Windows 7 that if you have a drive mapped that is not currently connected, Alpha takes a long time to save the component.

          It is not actually Alpha that takes a long time, but Windows 7 seems to take a long time. Probably because it is trying to resolve the unavailable drive.

          I'm sure there is a way around this, I haven't figured it out yet.

          I've also noticed that if I have a grid component that accesses a MySql db through a VPN, it is slow to save. Saves very fast when the db is local.

          Comment


            #6
            Re: Developer Edition - Build 3608 - CPU at 100%

            Been travelling.

            The point is that an open grid in development results in a 100% CPU utilization on one of an 8-core machine. It is not consistent so I cannot send a test grid in for evaluation.

            If I run across something that is consistent, I will be sure to send it in.
            Carl ~ Dallas, TX
            I'm so old that pool balls came with Roman Numerals

            Comment


              #7
              Re: Developer Edition - Build 3608 - CPU at 100%

              According to co-workers 1 server instance of alpha only uses 1 core. Not sure if this is a problem - but apparently you need more than 1 server instance to use more than 1 core.
              Scott Moniz - Computer Programmer/Analyst
              REA Inc.
              http://reainc.net
              (416)-533-3777
              [email protected]

              REA INC offers consulting services, programming services, systems design, database design, third party payment gateway integration (CHASE, PAYPAL, AUTHORIZE.NET) and developer support.
              If you need custom code, or 1-to-1 mentoring in any facet of your database/web application design,
              contact us to discuss options.

              Comment


                #8
                Re: Developer Edition - Build 3608 - CPU at 100%

                Has there been any explanation resolution to this issue?

                My processor is pinned (but system is responsive) even when I have Alpha5 minimized.

                Attached is a graph of processor activity, you can see at what point I shut Alpha down...

                Any suggestions?
                Thanks,
                Bill

                Comment


                  #9
                  Re: Developer Edition - Build 3608 - CPU at 100%

                  I notice the same or similar problem. Some thread seems to go wild and chew up 100% of a cpu. If you have multiple cpu, then other threads can run without much real contention. I see it come up after some time elapses and I may be in some other application when I hear the cpu fan kick to high and stay. Every time I go look, it is Alpha. I kill Alpha and cpus settle down.

                  Comment


                    #10
                    Re: Developer Edition - Build 3608 - CPU at 100%

                    I have the same problem on an older thinkpad. I have to shut down and restart alpha. I noticed I can recreate this problem by looking at Web Components in my project and then change to look at A5W pages. If I view All Files and do not change to Web Components or A5W pages I can usually go for a long time before the cpu usage pegs. Also the project files are on a network drive. This does not happen on my desktop machine.
                    Win 10 64 Development, Win 7 64 WAS 11-1, 2, Win 10 64 AA-1,2, MySql, dbForge Studio The Best MySQL GUI Tool IMHO. http://www.devart.com/dbforge/mysql/studio/

                    Comment


                      #11
                      Re: Developer Edition - Build 3608 - CPU at 100%

                      If I move to fast. Closing a grid and then opening another grid too fast will peg processor to 100% and requires me to kill Alpha and restart.

                      I am on Win XP.

                      Regards,

                      Michael Carroll

                      www.redrocksbluesky.com
                      www.theminimalistrunner.com
                      [email protected]
                      435-275-5170
                      Last edited by MichaelCarroll; 03-27-2011, 12:04 PM.

                      Comment


                        #12
                        Re: Developer Edition - Build 3608 - CPU at 100%

                        I'm using Vista, and I often have to kill alpha when I am on, for example the components list and have been duplicating or renaming components, then I switch to the page view or vice versa.

                        My work around is to always leave the list on "All files".

                        Pat
                        Pat Bremkamp
                        MindKicks Consulting

                        Comment


                          #13
                          Re: Developer Edition - Build 3608 - CPU at 100%

                          I wonder what the common denominator is.

                          It seems to occur during a disk access.

                          Could it be a wireless connection?

                          I tried to create a dump file but it is over 300 MB and the reader won't open it.

                          Here are some specs from my laptop that has the issues;

                          Intel Pentium M 2.0 GHZ
                          2 GB RAM
                          32 bit Vista
                          Wireless 54Mbps
                          Alpha project located on a network drive.
                          The local disk has plenty of free space.
                          Alpha 4091_3658
                          Compiler v 1600 same with 1200
                          Win 10 64 Development, Win 7 64 WAS 11-1, 2, Win 10 64 AA-1,2, MySql, dbForge Studio The Best MySQL GUI Tool IMHO. http://www.devart.com/dbforge/mysql/studio/

                          Comment


                            #14
                            Re: Developer Edition - Build 3608 - CPU at 100%

                            This has been a consistent issue for me as well. I have a dual core dedicated Win7 dev machine with MySQL running as a service. The more I save and publish grids etc the more I peg out on core 1. It seems the compiling process can render results but activity on the CPU continues on for some time.

                            I don't think this is a RAM issue since my memory will be running 25% at the same time that CPU0 is maxed???
                            Kim Dickerman

                            Comment


                              #15
                              Re: Developer Edition - Build 3608 - CPU at 100%

                              I'll add my voice to the ruckus here. I'm so tired of having everything pegged, drive screaming, and have to shut down and quit A5 20 times a day. This has been going on for a long time - not just the latest build.
                              -Steve
                              sigpic

                              Comment

                              Working...
                              X