Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-5910

slow sharding already existed collections

    • Type: Icon: Bug Bug
    • Resolution: Cannot Reproduce
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 2.1.1
    • Component/s: Sharding
    • Labels:
    • ALL

      Results of migration one chunk (default size: 64mb), collection with 180 million of rows

      by {_id}:      ~ 245 secs
      by {key}:      ~ 570 secs
      by {key, _id}: ~1100 secs
      

      where

      _id - ObjectId
      key - 32 chars - md5 hash
      

      Using next configuration

      3.75 GB memory
      2 EC2 Compute Unit (1 virtual core with 2 EC2 Compute Unit)
      410 GB instance storage
      32-bit or 64-bit platform
      I/O Performance: Moderate
      API name: m1.medium
      

      Even in the best case it is slow (245 secs)
      No concurrent read/write to database, just sharding

      "removeshard" is also not so fast

      Attach logs (iostat, mongostat, mongotop, vmstat, at some tests have mongo

      {db,s}

      logs)

      Related links:
      https://groups.google.com/d/msg/mongodb-user/ziPjlJIS5_w/WMG3iZSuB6kJ
      https://groups.google.com/d/msg/mongodb-user/R7XS1tDME8g/ucQR63ixmy0J

            Assignee:
            spencer@mongodb.com Spencer Brody (Inactive)
            Reporter:
            azat Azat Khuzhin
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: