[jira] [Commented] (IGNITE-3176) Need to create gc log for each client separately [ yardstick-ignite ]

2016-11-16 Thread Ilya Suntsov (JIRA)

[ 
https://issues.apache.org/jira/browse/IGNITE-3176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15670118#comment-15670118
 ] 

Ilya Suntsov commented on IGNITE-3176:
--

I told about a little different use case:
1. Set in properties file number of servers and drivers (drivers are clients if 
we set --client parameter, please take a look at attachment) e.g:
{noformat}
# Comma-separated list of the hosts to run BenchmarkServers on. 2 nodes on 
local host are enabled by default.
SERVER_HOSTS=localhost,localhost,localhost

# Comma-separated list of the hosts to run BenchmarkDrivers on. 1 node on local 
host is enabled by default.
DRIVER_HOSTS=localhost,localhost
{noformat}

2. bin/benchmark-run-all.sh config/benchmark.properties only in one terminal.

I this case we receive 2 gc files.

> Need to create gc log for each client separately [ yardstick-ignite ]
> -
>
> Key: IGNITE-3176
> URL: https://issues.apache.org/jira/browse/IGNITE-3176
> Project: Ignite
>  Issue Type: Bug
>  Components: clients, general
>Affects Versions: 1.6
>Reporter: Ilya Suntsov
>Assignee: Chandresh Pancholi
>Priority: Critical
> Fix For: 1.8
>
>
> In case when started more than one client/server on one host yardstick 
> re-write GC logs.
> GC options contain in *.properties files:
> {noformat}
> now0=`date +'%H%M%S'`
> # JVM options.
> JVM_OPTS=${JVM_OPTS}" -DIGNITE_QUIET=false"
> # Uncomment to enable concurrent garbage collection (GC) if you encounter 
> long GC pauses.
> JVM_OPTS=${JVM_OPTS}" \
> -Xloggc:./gc${now0}.log \
> -XX:+PrintGCDetails \
> -verbose:gc \
> -XX:+UseParNewGC \
> -XX:+UseConcMarkSweepGC \
> -XX:+UseTLAB \
> -XX:NewSize=128m \
> -XX:MaxNewSize=128m \
> -XX:MaxTenuringThreshold=0 \
> -XX:SurvivorRatio=1024 \
> -XX:+UseCMSInitiatingOccupancyOnly \
> -XX:CMSInitiatingOccupancyFraction=60 \
> {noformat}
> As you can see here will be created 1 log file and if you start another 
> driver/server with the same properties file will be re-write.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (IGNITE-3176) Need to create gc log for each client separately [ yardstick-ignite ]

2016-09-08 Thread Chandresh Pancholi (JIRA)

[ 
https://issues.apache.org/jira/browse/IGNITE-3176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15472976#comment-15472976
 ] 

Chandresh Pancholi commented on IGNITE-3176:


I tried reproducing the issue. Below are the steps
1. Run bin/benchmark-run-all.sh config/benchmark.properties in one terminal 
with 2 server hosts
2.Run bin/benchmark-run-all.sh config/benchmark.properties in another terminal 
with 2 server hosts

I have got 4 diff GC log file.

Let me know incase i missed any steps to reproduce it.


> Need to create gc log for each client separately [ yardstick-ignite ]
> -
>
> Key: IGNITE-3176
> URL: https://issues.apache.org/jira/browse/IGNITE-3176
> Project: Ignite
>  Issue Type: Bug
>  Components: clients, general
>Affects Versions: 1.6
>Reporter: Ilya Suntsov
>Priority: Critical
> Fix For: 1.8
>
>
> In case when started more than one client/server on one host yardstick 
> re-write GC logs.
> GC options contain in *.properties files:
> {noformat}
> now0=`date +'%H%M%S'`
> # JVM options.
> JVM_OPTS=${JVM_OPTS}" -DIGNITE_QUIET=false"
> # Uncomment to enable concurrent garbage collection (GC) if you encounter 
> long GC pauses.
> JVM_OPTS=${JVM_OPTS}" \
> -Xloggc:./gc${now0}.log \
> -XX:+PrintGCDetails \
> -verbose:gc \
> -XX:+UseParNewGC \
> -XX:+UseConcMarkSweepGC \
> -XX:+UseTLAB \
> -XX:NewSize=128m \
> -XX:MaxNewSize=128m \
> -XX:MaxTenuringThreshold=0 \
> -XX:SurvivorRatio=1024 \
> -XX:+UseCMSInitiatingOccupancyOnly \
> -XX:CMSInitiatingOccupancyFraction=60 \
> {noformat}
> As you can see here will be created 1 log file and if you start another 
> driver/server with the same properties file will be re-write.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)