Studio 5.1 getting slower.

Go To Last Post
21 posts / 0 new
Author
Message
#1
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Studio 5.1 is now so slow as to be unuseable.
I can almost type the complete works of Shakespeare before the first letter appears on the screen.
It's impossible to edit stuff, becuase I never know where the cursor should be(although it's a bit easier if I don't look at the screen).

I have tried turning VAssistX off, it makes little or no difference.

Compiling is fine, it's just editing the source that seems to be affected.

I am running Windows 7 64 bit pro on an Intel Duo 2.93 GHz with 8GB of RAM, but it feels like I'm working with a Babbage difference engine!

Any advice gratefully received!

Four legs good, two legs bad, three legs stable.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Go back to AS 4.19. Get a faster computer. :wink:

I have noticed that too, not only with AS5.1 but also with VS2010. Although AS5.1 is really slow now.

Sorry I can't help any further.

"I may make you feel but I can't make you think" - Jethro Tull - Thick As A Brick

"void transmigratus(void) {transmigratus();} // recursio infinitus" - larryvc

"It's much more practical to rely on the processing powers of the real debugger, i.e. the one between the keyboard and chair." - JW wek3

"When you arise in the morning think of what a privilege it is to be alive: to breathe, to think, to enjoy, to love." -  Marcus Aurelius

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

How about assigning the cpu affinity in task manager to the editor task?

Imagecraft compiler user

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

larryvc wrote:
Go back to AS 4.19. Get a faster computer. :wink:

I have noticed that too, not only with AS5.1 but also with VS2010. Although AS5.1 is really slow now.

Sorry I can't help any further.


Hmmph.
I don't think 4.19 will handle JTAG ICE3.
Faster computer is joke, yes?

John

Four legs good, two legs bad, three legs stable.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

John_A_Brown wrote:
Faster computer is joke, yes?

John

Yes and no. I'm Overclocked to 4.04 GHz on a 3.16 GHZ processor and I still want to go faster. Also 8GB memory. Lots of virtual machines running all at once. I have to kill most of them when I run AS5.1 or AS6. :)

"I may make you feel but I can't make you think" - Jethro Tull - Thick As A Brick

"void transmigratus(void) {transmigratus();} // recursio infinitus" - larryvc

"It's much more practical to rely on the processing powers of the real debugger, i.e. the one between the keyboard and chair." - JW wek3

"When you arise in the morning think of what a privilege it is to be alive: to breathe, to think, to enjoy, to love." -  Marcus Aurelius

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

John,

Try disabling graphics acceleration in the Tools->Options screen under "Visual Experience". If your graphics drivers are wonky or your PC old, this will actually decrease performance over just software rendering.

- Dean :twisted:

Make Atmel Studio better with my free extensions. Open source and feedback welcome!

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Quote:
If your graphics drivers are wonky or your PC old

How old is old? I have a Dell Optiplex that I bought about a year ago...

I'll try your suggestion, thanks.

Four legs good, two legs bad, three legs stable.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I'm talking ye-olde here, since some 'Freaks are still rocking systems from vintage 2001.

Incidentally, if that PC uses an integrated graphics chip that has the words "Intel" in it, then it's probably the cause; the earlier Intel "Extreme" graphics chips were actually much slower than software rendering. Yes, they managed to make a discrete graphics decellerator.

- Dean :twisted:

Make Atmel Studio better with my free extensions. Open source and feedback welcome!

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

OK, I've tried that.
I've also closed all other programs, including XP running in Virtual box.
I've tried disabling Avast anti-virus, Open Office starter, anything else that appears to be running.
No difference. Maybe it's a networking problem? Could Studio 5.1 be searching a network or something?

John

Four legs good, two legs bad, three legs stable.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Hrm. The only other suspect can think of is Visual Assist, as that fires on source editing - but you said you turned that off. What is the system processor and how much RAM do you have? Do you see CPU and RAM spikes corresponding to the slowness?

- Dean :twisted:

Make Atmel Studio better with my free extensions. Open source and feedback welcome!

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Quote:
What is the system processor and how much RAM do you have?

See first post.
Yes, I see CPU spikes.
I think I may have something re.networks. I just disable the network adapter, and the problem seemed to vanish. I will investigate further later.

Four legs good, two legs bad, three legs stable.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

John,

You may know this but the next game to play is to download a copy of Wireshark and see exactly what AS is trying to do with the network.

Cliff

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

No, I didn't know that. I'll check it out later, thanks.

BTW, what does "# Communication server listening on port 49683." in the Studio 5 output window mean, exactly?

Four legs good, two legs bad, three legs stable.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Quote:

BTW, what does "# Communication server listening on port 49683." in the Studio 5 output window mean, exactly?

Studio consists of two main parts, the front end, and the back end. The front end is the IDE, aka "the fancy text editor". The back end is the module which runs the simulator and communicates with the Atmel tools for programming and debugging. When you interact with the front end and request a back end operation, a message is sent to the back end through a local TCP connection.

The front and back ends connect through this local TCP connection so that the back end can be made into a completely separate process, making the system more modular. It's normal and nothing to worry about.

- Dean :twisted:

Make Atmel Studio better with my free extensions. Open source and feedback welcome!

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Dean,

But when editing/building that link is not been exercised is it? So should have no impact on just using the thing as an editor.

Cliff

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

clawson wrote:
Dean,

But when editing/building that link is not been exercised is it? So should have no impact on just using the thing as an editor.

Cliff

No, it should not...

I would look closer on the video driver. There are many weird things that may happen, especially with a ill behaving Intel chip, so at least make sure that the drivers are up to date...

:: Morten

 

(yes, I work for Atmel, yes, I do this in my spare time, now stop sending PMs)

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Quote:

But when editing/building that link is not been exercised is it? So should have no impact on just using the thing as an editor.

The avrdbg.exe process is spawned when Studio is started, so it is running when Studio is running. I'm not sure what communication is involved between the two on a regular basis, but I would guess at a minimum there would be some sort of communication to poll or receive events about tool insertion/detachment.

My explanation earlier was more of a "that's what that message means" statement than a "that's the issue" statement.

- Dean :twisted:

Make Atmel Studio better with my free extensions. Open source and feedback welcome!

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

abcminiuser wrote:
Quote:

But when editing/building that link is not been exercised is it? So should have no impact on just using the thing as an editor.

The avrdbg.exe process is spawned when Studio is started, so it is running when Studio is running. I'm not sure what communication is involved between the two on a regular basis, but I would guess at a minimum there would be some sort of communication to poll or receive events about tool insertion/detachment.

My explanation earlier was more of a "that's what that message means" statement than a "that's the issue" statement.

- Dean :twisted:

The backend is only used for tool detection if the "Use tool pooling" is active under options->debugger.
This is disabled by default...

The communication should not be an issue, as it mostly is setup parameters and debugging commands/events that is passed between the frontend and backend.

:: Morten

 

(yes, I work for Atmel, yes, I do this in my spare time, now stop sending PMs)

Last Edited: Tue. May 8, 2012 - 09:31 AM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

As far as I can tell, all my drivers are up to date.
I am guilty of using large source files(12,000 lines of C in this case), however, could that have some effect? It never bothered PN...

Four legs good, two legs bad, three legs stable.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

John_A_Brown wrote:
As far as I can tell, all my drivers are up to date.
I am guilty of using large source files(12,000 lines of C in this case), however, could that have some effect? It never bothered PN...

It does sound like a Visual Assist issue, but as you said, you have disabled it? Do you use UNC paths? There
are some speed issues when editing files on a mounted device, networkdrive etc...

:: Morten

 

(yes, I work for Atmel, yes, I do this in my spare time, now stop sending PMs)

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Further investigation: VAssist makes no difference. Network enabled/disabled no difference.
This is not slightly slow, it really hangs for seconds at a time!
It's a great way of encouraging typos, as you have no idea where the cursor is supposed to be!

Four legs good, two legs bad, three legs stable.