html_url,issue_url,id,node_id,user,user_label,created_at,updated_at,author_association,body,reactions,issue,issue_label,performed_via_github_app https://github.com/simonw/datasette/issues/694#issuecomment-595489222,https://api.github.com/repos/simonw/datasette/issues/694,595489222,MDEyOklzc3VlQ29tbWVudDU5NTQ4OTIyMg==,9599,simonw,2020-03-05T23:00:33Z,2020-03-05T23:00:33Z,OWNER,"The initial `datasette publish cloudrun` failed, now I can replicate that error by running: ``` gcloud run deploy --allow-unauthenticated --platform=managed \ --image gcr.io/datasette-222320/datasette non-profit-ethics ```","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",576582604,datasette publish cloudrun --memory option, https://github.com/simonw/datasette/issues/694#issuecomment-595489514,https://api.github.com/repos/simonw/datasette/issues/694,595489514,MDEyOklzc3VlQ29tbWVudDU5NTQ4OTUxNA==,9599,simonw,2020-03-05T23:01:35Z,2020-03-05T23:01:35Z,OWNER,"Aha! The logs said ""Memory limit of 244M exceeded with 247M used. Consider increasing the memory limit, see https://cloud.google.com/run/docs/configuring/memory-limits""","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",576582604,datasette publish cloudrun --memory option, https://github.com/simonw/datasette/issues/694#issuecomment-595490889,https://api.github.com/repos/simonw/datasette/issues/694,595490889,MDEyOklzc3VlQ29tbWVudDU5NTQ5MDg4OQ==,9599,simonw,2020-03-05T23:06:30Z,2020-03-05T23:06:30Z,OWNER,"This fixed it (I tried 1Gi first but that gave the same error): ``` gcloud run deploy --allow-unauthenticated --platform=managed \ --image gcr.io/datasette-222320/datasette non-profit-ethics --memory=2Gi ```","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",576582604,datasette publish cloudrun --memory option, https://github.com/simonw/datasette/issues/694#issuecomment-595491182,https://api.github.com/repos/simonw/datasette/issues/694,595491182,MDEyOklzc3VlQ29tbWVudDU5NTQ5MTE4Mg==,9599,simonw,2020-03-05T23:07:33Z,2020-03-05T23:45:38Z,OWNER,"So two things I need to do for this: * Add a `--memory` option to `datasette publish cloudrun` * Maybe capture this error and output a helpful suggestion that you increase the memory with that option? Not sure how feasible that is.","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",576582604,datasette publish cloudrun --memory option, https://github.com/simonw/datasette/issues/694#issuecomment-595492478,https://api.github.com/repos/simonw/datasette/issues/694,595492478,MDEyOklzc3VlQ29tbWVudDU5NTQ5MjQ3OA==,9599,simonw,2020-03-05T23:12:25Z,2020-03-05T23:12:25Z,OWNER,I wonder if there's some weird reason that we churn through too much RAM on initial datasette startup here? I wouldn't expect startup to use a huge spike of RAM. Maybe need to profile a bit.,"{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",576582604,datasette publish cloudrun --memory option, https://github.com/simonw/datasette/issues/694#issuecomment-595498926,https://api.github.com/repos/simonw/datasette/issues/694,595498926,MDEyOklzc3VlQ29tbWVudDU5NTQ5ODkyNg==,9599,simonw,2020-03-05T23:35:32Z,2020-03-05T23:35:32Z,OWNER,"Tested that with: ``` datasette publish cloudrun fixtures.db --memory 512Mi --service fixtures-memory-512mi ``` Here's the result in the Google Cloud web console: ","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",576582604,datasette publish cloudrun --memory option,