[
https://issues.apache.org/jira/browse/HDFS-7358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14207621#comment-14207621
]
stack commented on HDFS-7358:
-----------------------------
bq. I did it in some early patches but it did not work. The
Ok. Thanks. +1 then. According to the macro numbers above, the difference is
little if anything between no-sync and sync on Packet (latest patch and the
just previous):
{code}
Performance counter stats for '/home/stack/hbase/bin/hbase --config
/home/stack/conf_hbase
org.apache.hadoop.hbase.regionserver.wal.HLogPerformanceEvaluation -threads 100
-iterations 100000 -keySize 50 -valueSize 100':
560533.518789 task-clock # 3.583 CPUs utilized
18,884,751 context-switches # 0.034 M/sec
4,651,373 CPU-migrations # 0.008 M/sec
649,422 page-faults # 0.001 M/sec
849,474,024,940 cycles # 1.515 GHz
[83.31%]
647,838,434,834 stalled-cycles-frontend # 76.26% frontend cycles idle
[83.27%]
390,806,881,663 stalled-cycles-backend # 46.01% backend cycles idle
[66.68%]
395,809,837,047 instructions # 0.47 insns per cycle
# 1.64 stalled cycles per insn
[83.34%]
72,112,316,041 branches # 128.649 M/sec
[83.35%]
2,658,785,438 branch-misses # 3.69% of all branches
[83.40%]
156.430287629 seconds time elapsed
{code}
> Clients may get stuck waiting when using ByteArrayManager
> ---------------------------------------------------------
>
> Key: HDFS-7358
> URL: https://issues.apache.org/jira/browse/HDFS-7358
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: hdfs-client
> Reporter: Tsz Wo Nicholas Sze
> Assignee: Tsz Wo Nicholas Sze
> Attachments: h7358_20141104.patch, h7358_20141104_wait_timeout.patch,
> h7358_20141105.patch, h7358_20141106.patch, h7358_20141107.patch,
> h7358_20141108.patch
>
>
> [~stack] reported that clients might get stuck waiting when using
> ByteArrayManager; see [his
> comments|https://issues.apache.org/jira/browse/HDFS-7276?focusedCommentId=14197036&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14197036].
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)