瀏覽代碼

Don't close ObjectDatabase after parsing pack

The cached object databases should not require a close to release
their cached resources. Most object databases just return their
own reference for newCachedDatabase(), so a close() here kills
the real database's internal caches, and possibly underlying files,
resulting in poor performance for the callers of PackParser like
ReceivePack or FetchProcess trying to then go look up objects that
were just parsed, or that current references point to.

Change-Id: Ia4a239093866e5b9faf82744f729fb73f4373f1a
Signed-off-by: Shawn O. Pearce <spearce@spearce.org>
tags/v1.1.0.201109011030-rc2
Shawn O. Pearce 13 年之前
父節點
當前提交
bfa62d88d4
共有 1 個文件被更改,包括 0 次插入1 次删除
  1. 0
    1
      org.eclipse.jgit/src/org/eclipse/jgit/transport/PackParser.java

+ 0
- 1
org.eclipse.jgit/src/org/eclipse/jgit/transport/PackParser.java 查看文件

@@ -511,7 +511,6 @@ public abstract class PackParser {
inflater.release();
} finally {
inflater = null;
objectDatabase.close();
}
}
return null; // By default there is no locking.

Loading…
取消
儲存