Performance issue in parallel file metadata call invokes
- Dominant language
- Java
- Stars
- 41
- Forks
- 37
- PR merge metrics
- No merged PRs in 30d
Description
When concurrent connections are made to file metadata fetch api, response time grows exponentially
`
for (int i = 0; i < 20; i++) {
Thread t = new Thread(new Runnable() {
@Override
public void run() {
long tstartTime = System.currentTimeMillis();
FileMetadataResponse fileResourceMetadata = client.getFileResourceMetadata(FetchResourceMetadataRequest.newBuilder()
.setResourceId("remote-ssh-resource2")
.setResourceType("SCP")
.setResourceToken("local-ssh-cred")
.setTargetAgentId("agent0")
.build());
long tendTime = System.currentTimeMillis();
System.out.println("Thread " + Thread.currentThread().getName() + " Time " + (tendTime - tstartTime));
}
}, i + "");
t.start();
}
`
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the Java reproduction and the client.getFileResourceMetadata call using FetchResourceMetadataRequest, then trace the file metadata fetch API path. Run the concurrent example and measure each request's response time. Done means the response time no longer grows exponentially as concurrent metadata requests increase.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api, backend, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100