search for: dstop

Hi All. # cat /etc/redhat-release CentOS release 6.2 (Final) # uname -r 2.6.32-220.17.1.el6.centos.plus.x86_64 # rpm -qa | grep solr apache-solr-3.5.0-1.5... I have a solr installation which is invoked: /usr/bin/java -Xms25g -Xmx25g -DSTOP.PORT=8079 -DSTOP.KEY=mustard -Dsolr.solr.home=multicore -jar start.jar After start/when the java process is running: # free -m total used free shared buffers cached Mem: 32093 23975 8118 0 189 5736 -/+ buffers/cache:...

...00 99.15 Device: tps kB_read/s kB_wrtn/s kB_read kB_wrtn sda 1.00 0.80 3.20 4 16 dm-0 1.00 0.80 3.20 4 16 dm-1 0.00 0.00 0.00 0 0 **dstop** [root at correo ~]# dstat -cd --disk-util --disk-tps ----total-cpu-usage---- -dsk/total- sda- -dsk/total- usr sys idl wai hiq siq| read writ|util|reads writs 1 0 99 0 0 0| 20k 17k|0.14| 1 1 0 0 100 0 0 0| 0 0 | 0| 0 0 0 0 100 0 0 0| 0 0...

...sed separately from the instruction creation. Normally you have to create a generic virtual register with the correct output type. When a lot of intermediate values are needed, this can get pretty messy. There is an alternative provided, but I don’t think it’s really any better. You can construct a DstOp from an LLT, which will create a new register. You would then need to use the returned instruction, get the destination register from the output and use that. This doesn’t allow you to naturally compose operations by using the return value of a build* function to another. I also find this aspect to...

...ead >kB_wrtn >> sda 1.00 0.80 3.20 4 >16 >> dm-0 1.00 0.80 3.20 4 >16 >> dm-1 0.00 0.00 0.00 0 >0 >> >> >> **dstop** >> [root at correo ~]# dstat -cd --disk-util --disk-tps >> ----total-cpu-usage---- -dsk/total- sda- -dsk/total- >> usr sys idl wai hiq siq| read writ|util|reads writs >> 1 0 99 0 0 0| 20k 17k|0.14| 1 1 >> 0 0 100 0 0 0| 0 0 | 0|...

...sed separately from the instruction creation. Normally you have to create a generic virtual register with the correct output type. When a lot of intermediate values are needed, this can get pretty messy. There is an alternative provided, but I don’t think it’s really any better. You can construct a DstOp from an LLT, which will create a new register. You would then need to use the returned instruction, get the destination register from the output and use that. This doesn’t allow you to naturally compose operations by using the return value of a build* function to another. I also find this aspect to...

...tps kB_read/s kB_wrtn/s kB_read kB_wrtn > sda 1.00 0.80 3.20 4 16 > dm-0 1.00 0.80 3.20 4 16 > dm-1 0.00 0.00 0.00 0 0 > > > **dstop** > [root at correo ~]# dstat -cd --disk-util --disk-tps > ----total-cpu-usage---- -dsk/total- sda- -dsk/total- > usr sys idl wai hiq siq| read writ|util|reads writs > 1 0 99 0 0 0| 20k 17k|0.14| 1 1 > 0 0 100 0 0 0| 0 0 | 0| 0 0 > 0...

How can I tell if this is normal behaviour? Oracle imports are horribly slow, an order of magnitude slower than on the same hardware with a slower disk array and Solaris 9. What I can look for to see where the problem lies? The server is 99% idle right now, with one database running. Each sample is about 5 seconds. I''ve tried setting kernel parameters despite the docs saying that