Out of memory : Java Heap Space / Engine timeout

[ericproulx]

Hello,

We're experiencing problem with the engine. In our case, it always turns out to a

Out of Memory Exception

I modified the engine locally to add some heap space before starting Tailor. I only added these 2 java options

-Xms1024m -Xmx2048m

Now, the heap space problem seems to be resolved but I'm experiencing the CC::Analyzer::Engine::EngineTimeout

Here's the code to start analyzing docker run --interactive --tty --rm --env CODECLIMATE_CODE="$PWD" --env ENGINE_MEMORY_LIMIT_BYTES="4096000000" --volume "$PWD":/code --volume /var/run/docker.sock:/var/run/docker.sock --volume /tmp/cc:/tmp/cc codeclimate/codeclimate analyze --dev

Here's my .codeclimate file with running with the local engine

engines:
  tailor-eric:
    enabled: true
    exclude_paths:
    - DerivedData/**/*
    - petalmd/Automation\ Tests/**/*
    - petalmd/Supporting\ Files/**/*
    - PetalMD\ Integration\ Tests/**/*
    - PetalMD\ Unit\ Tests/**/*
    - PetalMD\ UI\ Tests/**/*
    - PetalMD\ Frameworks/**/*
    - petalmd/Images.xcassets/**/*
    - petalmd/Base.Iproj/**/*
    - petalmd/Frameworks/**/*
    - PetalMD.xcodeproj/**/*
    - PetalMD.xcworkspace/**/*
    - Pods/**/*
    - config/**/*
    - fastlane/**/*
    - features/**/*
    - "**.xib"
    - "**.storyboard"
    - "**.lock"
    - "**.ipa"
    - "**.rb"
    - "**.entitlements"
    - "**.strings"
    - "**.plist"
    - "Gemfile"
    - "Podfile"
ratings:
  paths:
  - "**.swift"

[alykhank]

@eproulx-petalmd we've now updated the version of Tailor for use with Code Climate to v0.9.0 and this should fix several performance/memory issues, could you please try again with the new version?

[ericproulx]

I will thanks

On Apr 26, 2016, at 12:11, Alykhan Kanji notifications@github.com wrote:

@eproulx-petalmd we've now updated the version of Tailor for use with Code Climate to v0.9.0 and this should fix several performance/memory issues, could you please try again with the new version?

— You are receiving this because you were mentioned. Reply to this email directly or view it on GitHub

[ericproulx]

Same thing :(

[mrb]

@eproulx-petalmd We're also working on tuning some things - we'll post news here.