Latency vs Throughput @Memories

Status
Not open for further replies.

ivlsi

Advanced Member level 3
Joined
Feb 17, 2012
Messages
883
Helped
17
Reputation
32
Reaction score
16
Trophy points
1,298
Visit site
Activity points
6,868
Hi All,

I was recently told that Latency and Throughput in the memory-based systems are the enemies of each another. So, if I want to improve the Latency then I need to pay by Throughput and vise verse.

Could someone explain why?

Thank you!
 

In memory generally the two latency are there...Read Latency and Write latency.....Means number of clock cycles required to do read/ write operation.....It is property of memory. n depends how memory architecture is....rd n WR latencies may be different or same...Basically you can not change the latency of memory until n unless you are designing a memory...
So if memory take more clock cycles for rd or wr (more latency)...then throughput will be less..
 

As with all/most digital systems, you can increase clock speed by dividing the "task" into multiple tasks (pipelining). Same thing as an assembly line. The time the "task" spends on the assembly line is the latency. In theory, you could endlessly increase the speed at which the "belt" runs by making the sub-task at each station smaller and smaller. However, the time it would take to pass by each station would also increay (higher latency).
 

Status
Not open for further replies.

Similar threads

Menu
Log in
Register
Cookies are required to use this site. You must accept them to continue using the site. Learn more…