Why is mongorestore painfully slow?

» mongodb » Why is mongorestore painfully slow?

By : Terry Rowe

Date : December 01 2020, 04:55 PM

like below fixes the issue This is very old thread, but I was having similar problem recently, possibly for different reason, and came upon this question.
If you happen to be running mongo on AWS, be sure to use the right instance and volume types.

code :

Share :

MySQL MyISAM table performance... painfully, painfully slow

By : user993616

Date : March 29 2020, 07:55 AM

I hope this helps you . What's the data type and purpose of columnX in the userdata table? It should be noted that any text data type (i.e excluding char, varchar) forces any temporary tables to be created on disk. Now since you're doing a straight join without conditions, grouping or ordering, it probably won't need any temporary tables, except for aggregating the final result.
I think it would also be very helpful if you show us how your indexes are created. One thing to remember is that while InnoDB concatenates the primary key of the table to each index, MyISAM does not. This means that if you index column name and search for it with LIKE, but still want to get the id of the page group; Then the query would still need to visit the table to get the id instead of being able to retrieve it from the index.

Painfully Slow DB2 Query

By : Aura Muñoz

Date : March 29 2020, 07:55 AM

With these it helps For starters, are all foreign key relationships indexed? (e.g., CMSDPR23.JE215000, CP.JEBOA, etc.
Second, LIKE forces a full table search. Can you index NMELASTBUS and NAME_FIRST (etc...) and check for matches?

Symfony 4 is painfully slow in DEV

By : musa

Date : March 29 2020, 07:55 AM

around this issue Since the provided answer is working with macOSX, only, but performance issues exist with Docker for Windows as well the preferred answer didn't help in my case. I was following different approach partially described in answers to similar questions here on SO.
According to Performance Best Practices folders with heavy load such as vendor and var in a Symfony application shouldn't be part of a shared mount. If you require to persist those folders you should use volumes instead.

code :

RUN mkdir /app && mkdir /symfony/{var,vendor}

COPY setup-symfony.sh /setup-symfony.sh

VOLUME /symfony/var
VOLUME /symfony/vendor

[ -e /app/var ] || ln -s /symfony/var /app/var
[ -e /app/vendor ] || ln -s /symfony/vendor /app/vendor

version: "3.5"
services:
  database:
    build:
      context: docker/mysql
    volumes:
      - "dbdata:/var/lib/mysql"
    environment:
      MYSQL_ALLOW_EMPTY_PASSWORD: 1

  application:
    depends_on:
      - database
    build:
      context: docker/lamps
    ports:
      - "8000:8000"
    volumes:
      - ".:/app:cached"
      - "var:/symfony/var"
      - "vendor:/symfony/vendor"
    environment:
      DATABASE_URL: mysql://dbuser:dbuser@database/dbname

volumes:
  dbdata:
  var:
  vendor:

docker exec -it IDofContainer /bin/sh

cp -Lr vendor vendor.dis

Rstudio is painfully slow

By : user971590

Date : March 29 2020, 07:55 AM

around this issue Suddenly, Rstudio is painfully slow, and now it is unusable. This means, I open it up and there is a lag of several seconds if I type anything. I have explored all the options I can come up with: 1. re-installing both R and Rstudio (although I am not 100% sure I could remove all components), 2. trying to reset settings.... the obvious things such as clearing the workspace and the console. , Just a guess, but ?gctorture says

code :

 Provokes garbage collection on (nearly) every memory allocation.
 Intended to ferret out memory protection bugs.  Also makes R run
 _very_ slowly, unfortunately.

gctorture(FALSE)

ZendFramework 2 - painfully slow?

By : HAMDA WAJID

Date : March 29 2020, 07:55 AM

I hope this helps . ZF2, due to its nature, has a lot of file-IO for every request. A single page load request to load a data set from a database with doctrine and display the results can result in the opening around 200 php files. (Run an xdebug cache grind and you can see how much time is spent checking for, and opening files. It can be substantial.)
Most of what's being opened is "small," and executes very quickly once it's been read off-disk, but the actual file-io itself can cause significant delays.