Why is my LR CC library 192GB?





I have been looking into why my Lightroom CC (not classic) library file is 192GB. When I click on 'show package contents' on 'Lightroom Library.lrlibrary' I get the following list:

 

![Screenshot 2020-05-05 at 20.36.08.png](https://community.adobe.com/t5/image/serverpage/image-id/89396i499B1A7A2FC0DE7F/image-size/large?v=1.0&px=999 "Screenshot 2020-05-05 at 20.36.08.png")

 

The top folder contains another folder called 'originals' which seems to contain all my RAW files for the past four years. I thought it was supposed to store RAW's in the cloud and therefore free up space on the computer? If so (and I have set my local cache setting to 10% of available space so I can work on recent images) then why would local storage be so high and why are there RAW files in there?

 

![Screenshot 2020-05-05 at 20.40.16.png](https://community.adobe.com/t5/image/serverpage/image-id/89401i0132495A44B872F3/image-size/large?v=1.0&px=999 "Screenshot 2020-05-05 at 20.40.16.png")

 

As you can see, I haven't asked it to keep original files on the computer.

 

Thanks.
I spoke to Adobe and in the end they deleted the .lrlibrary file and let it rebuild itself. Apparently it's normal that the application can download 0-5% of the original images from the server if some of them can't be converted into smart previews for whatever reason. My case was a bug. Either way, the answer is to rename or delete the file and let it rebuild on it's own.
Out of curiosity, what are the sizes of the files you’re trying to move? hi ricardo,

the default cache size for the player is 20% of the available ram.

you can use the following environment variable to override the default value (to 4096 mb in this example):

setenv sgc\_pref\_reader\_cache\_max\_size\_in\_mb 4096

i hope this helps.

eric it’s a limitation of network shares.

the proper display of jpg thumbnails has a dependency on the media library.   the media library is not created for network shares, only local storage.

some people have said that if you precede the jpg file name with a “.” that the problem will go away.

example… by default, if you run docker images you will get the size of each image. however, if you run docker ps you would not get the size of the running containers. to check the size of each running container what you could do is just use the --size argument of docker ps command. docker ps --size you would get the following output: container id image command created status ports names size d64a8112d00a nginx "nginx -g 'daemon of…" about an hour ago up about an hour 0.0.0.0:80->80/tcp nginx 12mb (virtual 127mb) ab81be326c31 eboraas/laravel "/usr/sbin/apache2ct…" 2 hours ago up 2 hours 80/tcp, 443/tcp laravel 92mb (virtual 509mb) that way you will be able to quickly tell which container exactly is consuming the most disk space. in case that you need to clear some space, i would recommend checking out this tutorial here on how to remove docker images, containers and volumes: https://www.digitalocean.com/community/tutorials/how-to-remove-docker-images-containers-and-volumes hope that this helps! and use retention: <https://apps.nextcloud.com/apps/files_retention> it might be that the drives were formatted as 1tb, if you do a factory restore it might format the drives to the 2tb. you will lose your data though. error correcting code memory differs from other rams in respect of security. you need ecc ram when working with high-value data as it protects against data corruption by automatically detecting single-bit small errors that may affect there is no need for a program to do that. 

here are some simple steps which you can follow:

1.right click on your taskbar and choose start task manager.

2.once task manager is opened go to "processes" tab. 

3.when at the processes tab search for .exe file. (maybe in your case it will look like loop.exe or something) 

4.once you have found it. just right-click on it and hover over to "set priority" option. 

5.here are several options. the default one will be "normal" so just set that to "below normal" or "low". (i would prefer setting it to "below normal" so that it does not act strangely) 

6.it's done now restart your program and check the amount of ram it is using.

i hope this helps you. if not leave a reply and i will figure out another solution. glad to help.:) it turned out there was a problem with storage within my server. it wasn’t a problem with cloudflare after all. [**exhentai.org**/g/1322859/dba684fb59/](https://exhentai.org/g/1322859/dba684fb59/)

 Attached: [yep that's going in the fap folder 2.png](//zagforums.com/file#/?post=891440&filename=yep+that%26%23039%3Bs+going+in+the+fap+folder+2.png) (624x511
257.88 KB, 269.72K)