Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Register
  • Sign in
  • O Open VDS
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
    • Locked files
  • Issues 28
    • Issues 28
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Terraform modules
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Open Subsurface Data Universe SoftwareOpen Subsurface Data Universe Software
  • Platform
  • Domain Data Management Services
  • Seismic
  • Open VDS
  • Issues
  • #62
Closed
Open
Issue created Aug 03, 2020 by Anatoly Yanchevsky@Anatoly

Reading from s3 stuck

I'm starting to test OpenVDS with AWS. After create container, I try to read it back. On my first vm_1 running test take 100% CPU and almost not using network, process is stuck. With vm_2 it work better, but not all time.

vm_1: t3.large (2 CPU, 8 GB RAM) vm_2: t3.x2large (8 CPU, 32 GB RAM)

I have questions:

  1. Did you have any recommendations to minimal vm configuration ?
  2. Can I disable 'aws_sdk_' logs without library change ?
  3. Do you have restrictions to data size for OpenVDS::VolumeDataAccessManager::RequestVolumeSubset ?

read_OVDS.cc

Assignee
Assign to
Time tracking