Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Pytorch 1.0.0 with Serverless and AWS Lambda timeout; Error in cpuinfoΒ #15213

@norahsakal

Description

@norahsakal

πŸ› Bug

I am running an image classification model with Serverless and AWS Lambda. Receiving following error upon calling the Serverless function; "Error in cpuinfo: failed to parse the list of present procesors in /sys/devices/system/cpu/present" - I did not misspell this, the spelling is copied from the error message I received and appear with the same spelling here;
https://github.com/pytorch/cpuinfo/blob/master/src/linux/processors.c

Suspected it might be something with Pytorch 1.0.0 so I switched back to Pytorch 0.4.1 which made it work.

To Reproduce

Steps to reproduce the behavior:

  1. Run Pytorch in a Lambda with following whl in the requirements.txt;
    Pillow==5.3.0
    PyYAML==3.13
    https://download.pytorch.org/whl/cpu/torch-1.0.0-cp36-cp36m-linux_x86_64.whl
    torchvision==0.2.1

  2. Load optional model and predict an image, this error should arise; "Error in cpuinfo: failed to parse the list of present procesors in /sys/devices/system/cpu/present"
    and you will also get a timeout from the Lambda, regardless of how long timeout that is chosen; "Process exited before completing request"

No stack trace available, I only receive "Error in cpuinfo: failed to parse the list of present procesors in /sys/devices/system/cpu/present"
and a timeout error; "Process exited before completing request"

Expected behavior

Expected image prediction from the model every time a new image is uploaded.

Environment

  • PyTorch Version (e.g., 1.0): 1.0.0
  • OS (e.g., Linux): Linux
  • How you installed PyTorch (conda, pip, source): pip3
  • Build command you used (if compiling from source):
  • Python version: 3.6
  • CUDA/cuDNN version: No CUDA
  • GPU models and configuration: No GPU
  • Any other relevant information: Deployed with Serverless and AWS Lambda, 3008 GB memory and 30 second timeout, works with Pytorch 0.4.1

Additional context

Suspected it might be something with Pytorch 1.0.0 so I switched back to Pytorch 0.4.1 which made the image prediction work.

Let me know if I can provide any additional information.

Metadata

Metadata

Assignees

Labels

cherry-pickedThis PR was cherry-picked onto a release branch from masterhigh prioritymodule: dependency bugProblem is not caused by us, but caused by an upstream library we use

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions