[SOLVED] Websphere caonfiguration/ IBM JVM: pure java works much more slower that in tomcat

Good day, all. I Met next problem: Work on project that need to deploy on different env with WAS and tomcat. WAS docer img used: common/base-ibm-websphere:8.0.0.10 - 8.0 Architecture: x86_64

 Name                  IBM WebSphere Application Server
Version               8.0.0.10
ID                    BASE
Build Level           cf101502.03
Build Date            1/16/15
Package               com.ibm.websphere.DEVELOPERSILAN.v80_8.0.10.20150116_1534
Architecture          x86-64 (64 bit)
Installed Features    IBM 64-bit SDK for Java, Version 6
                      EJBDeploy tool for pre-EJB 3.0 modules
                      Embeddable EJB container
                      Stand-alone thin clients and resource adapters

Tomcat docker img used: common/base-tomcat:7

java version "1.7.0_80"
Java(TM) SE Runtime Environment (build 1.7.0_80-b15)
Java HotSpot(TM) Server VM (build 24.80-b11, mixed mode)

From the start suppose something wrong going with WAS because it's much more slower with simplest request (x8 slower):

  long startMethodTime = System.nanoTime();
        long endMethodTime;
        long operationStartTime;
        long operationEndTime;
        Long result = 0L;
        Long resultSet = 0L;


        operationStartTime = System.nanoTime();
        List<ResultDTO> testDAOList = new ArrayList<ResultDTO>();
        for (int i = 0; i < 200000; i++) {
            ResultDTO testClass = new ResultDTO();
            testClass.setBody(String.valueOf(new Random().nextDouble()));
            testClass.setResult(String.valueOf(new Random().nextInt()));
            testClass.setSubject(String.valueOf(new Date()));

            testDAOList.add(testClass);
        }
        operationEndTime = System.nanoTime();
        String operationTime = String.valueOf(((operationEndTime -  operationStartTime) / 1000000));
        LOGGER.error("Creation object in cycle=" + operationTime);


        operationStartTime = System.nanoTime();
        for (ResultDTO testDAO : testDAOList) {
            result += testDAO.getResult().length();
        }
        operationEndTime = System.nanoTime();
        operationTime = String.valueOf((operationEndTime -  operationStartTime)/ 1000000);
        LOGGER.error("Incrementation in the loop of objects=" + operationTime);


        operationStartTime = System.nanoTime();
        Set<ResultDTO> sortedResults = new TreeSet<ResultDTO>(
                new Comparator<ResultDTO>() {
                    public int compare(ResultDTO r1, ResultDTO r2) {
                        int firstCompValue = (r1.getResult().length() + r1.getSubject().length()) % 2;
                        int secondCompValue = (r2.getResult().length() + r2.getSubject().length()) % 2;
                        return firstCompValue - secondCompValue;
                    }
                }
        );

        sortedResults.addAll(testDAOList);
        operationEndTime = System.nanoTime();
        operationTime = String.valueOf((operationEndTime -  operationStartTime) / 1000000);
        LOGGER.error("Sort  the Set of Objects=" + operationTime);

        for (ResultDTO testDAO : sortedResults) {
            resultSet += testDAO.getBody().length();
        }

        //Creation of 100 default objects
        long hundredObjectsCreationTime = 0;
        for (int i = 0; i < 100; i++) {
            operationStartTime = System.nanoTime();
            ResultDTO testClass = new ResultDTO();
            testClass.setBody(String.valueOf(new Random().nextDouble()));
            testClass.setResult(String.valueOf(new Random().nextInt()));
            testClass.setSubject(String.valueOf(new Date()));
            operationEndTime = System.nanoTime();

            hundredObjectsCreationTime += (operationEndTime -  operationStartTime);
        }

        LOGGER.error("100 objects creation time = " + hundredObjectsCreationTime);

        endMethodTime = System.nanoTime();
        operationTime = String.valueOf((endMethodTime - startMethodTime) / 1000000);
        LOGGER.error("Test method duration = " + operationTime);

It's executed on WAS in x8 slower than on Tomcat. Test results for comporation:

    Tomcat:
2018-03-26 21:39:44,347 ERROR [c.v.e.r.r.AboutResource] Creation object in cycle=1006
2018-03-26 21:39:44,381 ERROR [c.v.e.r.r.AboutResource] Incrementation in the loop of objects=33
2018-03-26 21:39:44,411 ERROR [c.v.e.r.r.AboutResource] Sort  the Set of Objects=29
2018-03-26 21:39:44,411 ERROR [c.v.e.r.r.AboutResource] 100 objects creation time = 405100 - microsec
2018-03-26 21:39:44,411 ERROR [c.v.e.r.r.AboutResource] Test method duration = 1070

WAS:

[26/03/18 22:26:39:944 UTC] 00000018 SystemOut     O ERROR [c.v.e.r.r.AboutResource] Creation object in cycle=8408
[26/03/18 22:26:40:069 UTC] 00000018 SystemOut     O ERROR [c.v.e.r.r.AboutResource] Incrementation in the loop of objects=124
[26/03/18 22:26:40:373 UTC] 00000018 SystemOut     O ERROR [c.v.e.r.r.AboutResource] Sort  the Set of Objects=303
[26/03/18 22:26:40:377 UTC] 00000018 SystemOut     O ERROR [c.v.e.r.r.AboutResource] 100 objects creation time = 3384400
[26/03/18 22:26:40:377 UTC] 00000018 SystemOut     O ERROR [c.v.e.r.r.AboutResource] Test method duration = 8841

On the WAS side configured only heap size (more than enoph) and db connection (that don't relate to this question).

ON what first of all I should pay attention when tuning IBM jVM / WAS configuration? (now i'm already investigating IBM manuals, possible u save my time for avoid smoke testing different not effective JVM properties).