PowerVCS Forum
November 23, 2024, 12:30:23 PM
Welcome,
Guest
. Please
login
or
register
.
1 Hour
1 Day
1 Week
1 Month
Forever
Login with username, password and session length
Home
Help
Search
Login
Register
PowerVCS Forum
>
PowerVCS - PowerBuilder Integration
>
General Discussion
>
Refresh Status vs. Get Latest Version Performance
Pages: [
1
]
« previous
next »
Print
Author
Topic: Refresh Status vs. Get Latest Version Performance (Read 8905 times)
Phil Wallingford
Global Moderator
Newbie
Posts: 49
Refresh Status vs. Get Latest Version Performance
«
on:
September 21, 2009, 02:12:44 PM »
When PowerBuilder populates the list of objects for a Get Latest Version it is querying the source control system (PowerVCS or anyone else) one object at a time. When PB performs a Refresh Status it is querying source control in batches (25 at a time). As a consequence the Get Latest Version is 6-10 times slower. The basic operation is the same, so I don’t know why both couldn’t perform the same way. I have a call into my PB source control expert at Sybase and he should shed some light on this.
In the meantime I’ve seen that both operations place the results in a cache so that if you call Get Latest Version a second time, the response is immediate. This suggests a workaround for now. If you first Refresh Status, the results, produced relatively quickly, are placed in the cache and if you then call Get Latest, the list of objects appears immediately.
Regards,
Phil Wallingford
PowerVCS
Logged
Pages: [
1
]
Print
« previous
next »
Jump to:
Please select a destination:
-----------------------------
PowerVCS - General
-----------------------------
=> General Discussion
-----------------------------
PowerVCS - PowerBuilder Integration
-----------------------------
=> General Discussion
-----------------------------
PowerVCS - Development
-----------------------------
=> Enhancement Requests
=> Change Log
Loading...