Known limits There are multiple repo size limits which apply. Soft limit As of 2022, as per the docs, this is 5 GB. If you exceed this limit, is possible that you will receive an email from GitHub Support. We recommend repositories remain small, ideally less than 1 GB, and less than 5 GB is … Read more
Disk space is not the issue… but memory and performance will be. Double the page reads, double index size, strange LIKE and = constant behaviour etc Do you need to store Chinese etc script? Yes or no… And from MS BOL “Storage and Performance Effects of Unicode” Edit: Recent SO question highlighting how bad nvarchar … Read more
The modular crypt format for bcrypt consists of $2$, $2a$ or $2y$ identifying the hashing algorithm and format a two digit value denoting the cost parameter, followed by $ a 53 characters long base-64-encoded value (they use the alphabet ., /, 0–9, A–Z, a–z that is different to the standard Base 64 Encoding alphabet) consisting … Read more
One word answer: MONEY 😀 1 GB to store in US-East-1: (Updated at 2016.dec.20) Glacier: $0.004/Month (Note: Major price cut in 2016) S3: $0.023/Month S3-IA (announced in 2015.09): $0.0125/Month (+$0.01/gig retrieval charge) EBS: $0.045-0.1/Month (depends on speed – SSD or not) + IOPS costs EFS: $0.3/Month Further storage options, which may be used for temporary … Read more
It’s a difference between RDBMS’s varchar (or similar) — those are usually specified with a maximum length, and might be more efficient in terms of performance or storage — and text (or similar) types — those are usually limited only by hardcoded implementation limits (not a DB schema). PostgreSQL 9, specifically, states that “There is … Read more
I’m in charge of some applications that manage many TB of images. We’ve found that storing file paths in the database to be best. There are a couple of issues: database storage is usually more expensive than file system storage you can super-accelerate file system access with standard off the shelf products for example, many … Read more