javascript - AWS Lambda Duration vs Function run time -


i noticed duration vs function run time issue in cloud watch log nodejs lambda function. using serverless plugin deploy/code functions.

this lambda function code:

module.exports.handler = function (event, context, cb) {     console.time("function_run_time");     myfunction(function (callback) {        console.timeend("function_run_time");        return cb(null, callback)     }); };

in cloud watch logs im getting following

2016-05-25t00:18:58.881z    45cd0785-ccce-11e6-818f-cb61404e173c    function_run_time: 477ms  report requestid: 45cd0785-ccce-11e6-818f-cb61404e173c  duration: 1866ms    billed duration: 1900 ms memory size: 1024 mb   max memory used: 39 mb

i wondering why function run time @ 477ms duration @ 1866ms.

is there in code need call end lamdba function earlier?

thanks

check if have code running after calling callback see here: aws lambda

by default, callback wait until node.js runtime event loop empty before freezing process , returning results caller. can set property false request aws lambda freeze process after callback called

also if using older version of node lambda should call context.succeed(); , context.fail(error) end function.


-

Comments

Post a Comment

Popular posts from this blog

scala - 'wrong top statement declaration' when using slick in IntelliJ -

Image
i'm porting project scala 2.9 2.10, therefore have use slick instead of scalaquery. i'm using slick 2.1.0 since supports ms access. according this tutorial , upgrade guide changed robs object class , added val robs : why error message wrong top statement declaration , how rid of it? edit: i'm new scala... according this question seems can't put val outside of methods or classes, right? code above directly in packge. right approach slick then? should move code in class or trait? according this changed val robs = tablequery[robs] to object robs extends tablequery(new robs(_)) {} . no warnings or errors anymore. :)
Read more

c# - DevExpress.Wpf.Grid.InfiniteGridSizeException was unhandled -

Image
when using devexpress, see error: devexpress.wpf.grid.infinitegridsizeexception unhandled message="by default, infinite grid height not allowed since grid rows rendered , hence grid work slowly. fix issue, should place grid container give finite height grid, or should manually specify grid's height or maxheight. note can avoid exception setting gridcontrol.allowinfinitegridsize static property true, in case grid run slowly." the problem dxgrid has infinite height. to fix, set height non-infinite. snoop absolutely invaluable this: if "height" xaml element infinite (i.e. 0 or nan ), can set using one of following: option 1: height="{binding path=actualheight, relativesource={relativesource mode=findancestor, ancestortype=uielement}}" option 2: verticalalignment="stretch" option 3: height="auto" hint: use verticalalignment="stretch" if child of grid <rowdefinition height=
Read more

PySide and Qt Properties: Connecting signals from Python to QML -

i trying run simple pyside appliccation design made in qml. call function in qml python in separated thread. i have following qml view: import qt 4.7 rectangle { visible: true width: 100; height: 100 color: "lightgrey" text { id: datestr objectname: "datestr" x: 10 y: 10 text: "init text" font.pixelsize: 12 function updatedata(text) { datestr.text = qstr(text) console.log("you said: " + text) } } } here application: some imports.... #!/usr/bin/python import sys import time pyside import qtdeclarative, qtcore pyside.qtgui import qapplication pyside.qtdeclarative import qdeclarativeview the qthread worker.... #worker thread class worker(qtcore.qthread): updateprogress = qtcore.signal(int) def __init__(self, child): qtcore.qthread.__init__(self) self.child = child def run(self):
Read more