Arm Community
Site
Search
User
Site
Search
User
Support forums
Arm Development Studio forum
RVDS 3.1 - Low Performance using node-locked license
Jump...
Cancel
Locked
Locked
Replies
4 replies
Subscribers
118 subscribers
Views
3560 views
Users
0 members are here
Options
Share
More actions
Cancel
Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion
RVDS 3.1 - Low Performance using node-locked license
Paulo Veronez
over 12 years ago
Note: This was originally posted on 20th June 2013 at
http://forums.arm.com
Hello everybody.
[size=2]I'm working with a legacy application that is compiled with RVDS 3.1 build 1021. [/size]
We have an environment with a license server with 6 floating licenses and one client machine that also have a node-locked license.
I supposed that compiling with a node-locked license would give me better performance. But the compilation time is the triple of the time when I use the license server at the same machine.
[size=2]I believe that I have a unknown problem with this node-locked license. [/size]
[size=2]Am I wrong about the performance using node-locked license?[/size]
Is there a way to improve the performance using this node-locked license?
Parents
Paulo Veronez
over 12 years ago
Note: This was originally posted on 24th June 2013 at
http://forums.arm.com
The network drives were disabled and the compilation time was reduced to 3 hours. However, the compilation time using the floating license is 2,5 hours.
I supposed that using a node-locked license would be faster than the floating license server. Am I wrong?
Cancel
Vote up
0
Vote down
Cancel
Reply
Paulo Veronez
over 12 years ago
Note: This was originally posted on 24th June 2013 at
http://forums.arm.com
The network drives were disabled and the compilation time was reduced to 3 hours. However, the compilation time using the floating license is 2,5 hours.
I supposed that using a node-locked license would be faster than the floating license server. Am I wrong?
Cancel
Vote up
0
Vote down
Cancel
Children
No data