alapha23 opened a new pull request #214: [NEMO-385]LambdaPass, LambdaPolicy and 
ResourceLambdaProperty
URL: https://github.com/apache/incubator-nemo/pull/214
 
 
   JIRA: [NEMO-385: Support Lambda Pass with lambda policy and lambda resource 
property](https://issues.apache.org/jira/browse/NEMO-385)
   
   **Major changes:**
   - Implement LambdaPass, LambdaPolicy and ResourceLambdaProperty
   
   **Tests for the changes:**
   - No test suites implemented
   
   **Other comments:**
   - This issue is a subissue under [NEMO-352 Nemo on AWS 
Lambda](https://issues.apache.org/jira/projects/NEMO/issues/NEMO-352)
   - This PR relates to GSoC2019
   
   **Build Command**
   `mvn clean && mvn install -T 2C -Dmaven.test.skip=true -Dcheckstyle.skip 
-Dmaven.javadoc.skip=true -Drat.skip=true -pl 
\!compiler/frontend/spark,\!examples/spark,\!examples/beam`
   
   **Execute Command**
   
   ```
   TIMEOUT=30
   WINDOW=30
   INTERVAL=30
   EVENTS=0
   PARALLELISM=1
   PERIOD=50
   NORMAL=10
   BURSTY=10
   CPU_DELAY=0
   SAMPLING=0.9
   
   ENABLE_OFFLOADING=false
   ENABLE_OFFLOADING_DEBUG=false
   POOL_SIZE=0
   FLUSH_BYTES=$((10 * 1024 * 1024))
   FLUSH_COUNT=10
   
   ./bin/run_nexmark.sh \
           -job_id nexmark-Q0 \
           -executor_json 
`pwd`/examples/resources/executors/beam_test_executor_resources.json \
           -user_main org.apache.beam.sdk.nexmark.Main \
           -optimization_policy 
org.apache.nemo.compiler.optimizer.policy.LambdaPolicy \
           -scheduler_impl_class_name 
org.apache.nemo.runtime.master.scheduler.StreamingScheduler \
           -user_args "--runner=org.apache.nemo.client.beam.NemoRunner 
--streaming=true --query=$1 --manageResources=false --monitorJobs=true 
--streamTimeout=$TIMEOUT"
   ```

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


With regards,
Apache Git Services

Reply via email to