Hey @gio, trying to dig into this a bit

SST needs some speed up

By slow, do you mean the handler function is taking long to run locally in

sst start

?

RAM reach 4gb

Can you see which process is this? Is it

esbuild

?

hello @Frank, as I said SST is running through Webstorm, it needs much time to show “Listening Request”. I can’t see “esbuild” process in my process list (I run ps aux) but the process which consume much resources is “webstorm” process. I think there is some optimization to make to work properly with webstorm because the “indexing processing” is invoked several times (and until finished it is impossible to make any action on code)

I'm not sure of the specifics, but I'll ask

it needs much time to show “Listening Request”

Is it also slow if you stop the

sst start

debug process and restart it?

yes it will be started fast, the only problem is during the execution (for indexing problem) and sometimes after a deploy (but it’s not a problem)

By “during the execution”, do you mean the indexing problems happens when executing the Lambda locally when a request comes in?

yes

hmm.. It consumes ~70MB for me

It sit at root

I see.. and are you setting

srcPath

for your functions?

export class VehiclesApi extends sst.Api {
    constructor (stack: sst.Stack, app: <http://sst.App|sst.App>, id: string) {
        const definition: ApiProps = {
            accessLog:
                '$context.identity.sourceIp,$context.requestTime,$context.httpMethod,$context.routeKey,$context.protocol,$context.status,$context.responseLength,$context.requestId',
            customDomain: {
                domainName: apigatewayv2.DomainName.fromDomainNameAttributes(
                    stack,
                    'vehicles-api-domain',
                    {
                        name: '<http://api.dev.irent-autonoleggio.com|api.dev.irent-autonoleggio.com>',
                        regionalDomainName: '<http://app.dev.irent-autonoleggio.com|app.dev.irent-autonoleggio.com>',
                        regionalHostedZoneId: '<http://dev.irent-autonoleggio.com|dev.irent-autonoleggio.com>',
                    }
                ),
                path: 'vehicles'
            },
            defaultAuthorizationType: ApiAuthorizationType.AWS_IAM,
            defaultFunctionProps: {
                timeout: 300,
                environment: {
                    STAGE: app.stage
                }
            },
            routes: {
                'POST   /'                          : 'src/vehicles-api/vehicles-api.createVehicle',
                'GET    /{uri}'                     : 'src/vehicles-api/vehicles-api.readVehicle',
                'PUT    /{uri}'                     : 'src/vehicles-api/vehicles-api.updateVehicle',
                'DELETE /{uri}'                     : 'src/vehicles-api/vehicles-api.deleteVehicle',
                'GET    /'                          : {
                    authorizationType: ApiAuthorizationType.NONE,
                    function: 'src/vehicles-api/vehicles-api.findVehicle',
                },
                'GET    /{start_date}/{end_date}'   : {
                    authorizationType: ApiAuthorizationType.NONE,
                    function: 'src/vehicles-api/vehicles-api.listAvailableVehicles',
                },
            }
        };
        super (stack, id, definition);
        this.attachPermissions(['dynamodb']);
    }
}

This is my API definition

Here’s my esbuild process in activity monitor

Hey @David Martin what’s ur SST version? We rolled out a fix addressing the esbuild memory usage recently.

0.35.1

Yup

beautiful

lol all good 👍

thanks Frank 🙌