Working with Amazon ElastiCache for RedisIr al Laboratorio
Could use a little more time for this - the data distro to redis can take a bit longer than expected
satisfied, but I was unable to finish it due to an unexpected commitment that pulled me away from it. Would be nice if one could use the same code for the same account and lab, maybe within a 12 hour window or something like that.
Very interesting. Will be useful for my company's database caching.
time not enough
A very nice exercise, however it must have more time! We got almost to the end (step 86) but the process of copying data from mysql to redis simply takes too long, and the lab was closed on us! SHAME.
lab worked fine, set up was fine. Just not sure I 100% understand what elastecashe is doing still
you had questions at the end... how long did each query take to run...why do you think they run more quicky? I don't know...please tell me
This lab felt more unpolished than some of the other ones I've done. There were several steps where there were long waits, which weren't clearly identified in the text. PuTTY kept timing out. 250000 rows was a little bit too slow to load into Redis using the python script, my PuTTY timed out towards the end, and the load progress didn't finish (DBSIZE didn't quite get to 250000). The Redis commands were not explained at all - there should have been a paragraph talking about what they are doing. The numbers that are output after running the commands are completely obscure and it isn't at all clear that the Redis is doing the same thing as the SQL, and the SQL query is unnecessarily complicated with an inner subquery to figure out the max acq date. And Redis didn't really give the timing statistics to even know that it's running faster than the SQL.
Tried EVERYTHING to connect through putty. So I did not learn anything from this
In "64.For Security group～", I can not click "Security group" and lab(vpc-XXX).
I can not it because of timeover in DBSIZE.