TeeInputStream.read(byte, int, int) line: 111 LargePackedDeltaObject$2(DeltaStream).read(byte, int, int) line: 215īufferedInputStream.read1(byte, int, int) line: not availableīufferedInputStream.read(byte, int, int) line: not available LargePackedDeltaObject$2(DeltaStream).read(byte, int, int) line: 214 LargePackedDeltaObject$2(DeltaStream).seekBase() line: 338 IO.skipFully(InputStream, long) line: 330 InflaterInputStream.skip(long) line: not availableīufferedInputStream.skip(long) line: not available ![]() InflaterInputStream.read(byte, int, int) line: not available Inflater.inflate(byte, int, int) line: not available Inflater.inflateBytes(long, byte, int, int) line: not available Robin, we debugged the whole reset operation of our repo and we never passed the code you mention above.Ī typical stack trace while the slow operation is in progress is the following: ![]() Please let us know if we can provide any additional information to resolve this issue. We tried to create a smaller repo and packed it to reproduce the issue, but with this repo JGit didn't go into method above at all. The same problem does not exist with the command line if we clone the same repo. Each piece takes 2 seconds or more, which results in more than one hour to checkout the 300 KB file. Within the debugger we see that there are *many* recursive calls to DeltaStream.read(byte,int,int) fetching very small pieces of the files in questions (like '11,11,"",60,22630642', or just "2"). The problematic files are 300 KByte CSV files with many very similar records, see example snippet attached. We debugged the issue and found that the problem is related to the checkout of certain files which take *very* long time. 1.5min), but then hangs forever at 100% progress. ![]() The clone of our 1.1 GB repo goes through quickly (approx. The problem happens with the checkout (and reset) after the initial clone. Hi, we are currently evaluating EGit for a large development project at Swiss Railways (SBB) and encountered an performance blocker with EGit/JGit. Example snippet out of the problematic files
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |