[jira] [Commented] (AMBARI-19058) Perf: Deploy 3000 Agent cluster and find perf bugs

["Hudson (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/AMBARI-19058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15722316#comment-15722316 ] 

Hudson commented on AMBARI-19058:
---------------------------------

SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #453 (See [https://builds.apache.org/job/Ambari-branch-2.5/453/])
AMBARI-19058. Perf: Deploy 3000 Agent cluster and find perf bugs. Part (vbrodetskyi: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=8f26728cc65bff6f67616657143f082fab9283fd])
* (edit) contrib/utils/perf/deploy-gce-perf-cluster.py


> Perf: Deploy 3000 Agent cluster and find perf bugs
> --------------------------------------------------
>
>                 Key: AMBARI-19058
>                 URL: https://issues.apache.org/jira/browse/AMBARI-19058
>             Project: Ambari
>          Issue Type: Task
>          Components: ambari-server
>    Affects Versions: 2.5.0
>            Reporter: Vitaly Brodetskyi
>            Assignee: Vitaly Brodetskyi
>             Fix For: 2.5.0
>
>         Attachments: AMBARI-19058_part1.patch
>
>
> Use Ambari 2.5 branch instead of trunk to deploy 2000-3000 agents on GCE and start finding perf bugs in the following areas.
> Agent registration (batches of 600 at a time are still very slow)
> Alerts
> Commands like starting/restarting/rolling restart, etc.
> Memory leaks after letting it run for a week?
> We may need to also run a memory profiler on the java process.



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