That agentgit.db is used by Agent Git to track MS-SCCI style check-outs, check-ins and locking.The first time I use Agent Git in my PowerBuilder workspace, it generates a .git folder containing among other things a file named agentgit.db.
So that file is not required to be there initially as Agent Git will create that file on demand.
This could be a bug in Agent Git.This first run is slow.
In the Agent Git configuration utility there are these two 'debug only' options:
a. Help debug the Git setup with extra logging information
b. Measure Git duration
If you turn on these two options extra debug information gets written to the log file.
You can find the location of that log file using the View Debug Log file button.
If you turn on those two options, repeat the slowdown in PoweBuilder and then send through the log file as an e-mail attachment I'd be happy to see if there is something going wrong in Agent Git itself.
As a example as to what to expect, I created a test project in Visual Studio, check that project into Git using Agent Git and saw the following Visual Studio output:
That output shows the checking too 5 seconds to complete and that is the sort of response time I would expect to see.---- Operation started at time 8:39:49 AM ----
---- Operation completed successfully at time 8:39:55 AM ----
Yes you can.Is there anyway to generate those files outside of PowerBuilder (i.e., from a command line)?
For example you could use something like TortoiseGit to manage these Git projects or even just the git.exe command client line tool.
For example running these git.exe commands would create a similar .git folder:
Code: Select all
git init git add -A git commit -m 'Added my project'
The fix for this slowness is two fold:
- Download the latest version of the Agent Git software from here: https://www.zeusedit.com/agentgit/download.html
- Apply the PowerBuilder performance tweaks as described here: https://www.zeusedit.com/agentgit/ide/pb/pb-2017.html