Skip to main content

SSD Vs. HDD

SSD (Solid State Drive) has generated lot of buzz in the market in the recent years and lots of companies are offering SSD based laptops. There are few reasons why SSD's are becoming popular:

a. Damn Fast
b. Flash memory based.
c. Increased battery life
d. No noise.

But it has few disadvantages:

a. They are costly.
b. The cells which are used in the SSD to store the data has a limited read write capacity.

Recently, I upgraded my MACBook Pro with Samsung SSD EVO series and I have no regrets. The performance of the system is amazing fast. For e.g.

a. Microsoft Word that took 1 minute to open in MACOSX now takes 3 seconds.
b. EI Capitan which use to take 40-minutes to 1 hour to Install, now does the same in 20 minutes.

I will recommend to upgrade your PC / laptop to SSD in case you are seeing a bottleneck in the performance. Don't go for the RAM Upgrade in case you are already having 4 -8 GB, rather upgrade to SSD. You won't regret.

Highly Recommended.

Comments

Unknown said…
Great Post ... Very informative :-)
April 1, 2016 at 9:34 PM
Unknown said…
Great Post ... Very informative :-)
April 1, 2016 at 9:34 PM
Post a Comment

Popular posts from this blog

Connecting Nodejs to SQL Server with Knex ORM - Part 1

Normally we connect Nodejs to the databases like SQLite, MongoDB, Postgres etc . In this multiple part post, I am going to show you, how we can connect Nodejs with Microsoft's SQL Server using Knex and run CRUD operations. 1. Installation of required packages In order to connect Nodejs to SQL Server with Knex, we will need following node packages installation: i. npm install knex ii. npm install mssql Once the packages are installed, we can write the following code to connect: //Code to KNEX connection settings. var knex = require('knex')({ client: 'mssql', connection: { user: 'sa', password: 'pwd', server: 'localhost', database: 'Test' } }); //Code to query the Table DEPT knex.select("*").from("dept") .then(function (depts){ depts.forEach((dept)=>{ //use of Arrow Function console.log({...dept}); }); }).catch(function(err) { ...
Post a Comment
Read more

SQLServer Error: 15404, Could not obtain information about Windows NT group/user Error code 0x5. [SQLSTATE 42000] (ConnIsLoginSysAdmin)

If we encounter this error "SQLServer Error: 15404, Could not obtain information about Windows NT group/user Error code 0x5. [SQLSTATE 42000] (ConnIsLoginSysAdmin)" in SQL Server in which the job fails because of the user account related problem, then we need to take the following steps to make it work: a. Go to SQL Server Agent. b. Then select the job which is giving error and not running successfully. c. Then choose properties and in the General Tab, change the owner to "SA" or any account that has the administrative privileges. The problem will be resolved.
1 comment
Read more

MAX pool size reached in ASP.NET

If you are handling large databases and big application(s) that are running on servers in a cluster, then probably this error might have occurred. In an ASP.NET app, we can use connection pooling that helps to share the connection between multiple request(s) rather than creating more connections. The settings relating to connection pool are defined in web.config file. Max pool size reached error in ASP.NET occurs, when the number of connections go beyond the maximum defined limit in Web.config file. Following are the various settings of the Connection Pooling: Name Default Description Connection Lifetime 0 When a connection is returned to the pool, its creation time is compared with the current time, and the connection is destroyed if that time span (in seconds) exceeds the value specified by  Connection Lifetime . This is useful in clustered configurations to force load balancing between a runnin...
Post a Comment
Read more