Hello, Its no bother. Thank you! I have learnt a lot from you guyz!
On Sun, Mar 2, 2014 at 5:27 PM, Andreas Kuhne <[email protected]>wrote: > Hi, > > I really don't know if they exist. Check redis.io, you should be able to > see them there. > > Regards, > > Andréas > > > 2014-03-01 21:48 GMT+01:00 Robin Lery <[email protected]>: > >> Ok, I think I get it now. Thank you so much! Just one more question >> though, does redis has feature similar to *getidentifiable()* and >> *putifuntouched() >> *like memcache, I think these are for consistency? >> >> >> On Sun, Mar 2, 2014 at 2:09 AM, Andreas Kuhne <[email protected] >> > wrote: >> >>> Ok, >>> >>> Redis and Memcache really solve the same problems. The main difference >>> is that you can use redis as a session cache for django (save the session >>> objects to memory instead of the database), which I haven't found a >>> solution for memcache yet. Also redis CAN be persisted (saved to disk), if >>> you setup your own redis server. >>> >>> But otherwise, you can use both memcache and redis for your cache. >>> Examples where a cache can be useful: >>> 1. You want to do a complex database query that takes a long time to >>> run, but doesn't update often. Just cache the results and use the result if >>> it is present. >>> 2. You can also cache the result of a view. If the view takes a long >>> time to render AND is the same for all users, then cache the entire view >>> result. >>> 3. There is also the possibility to create portions of a template and >>> cache just those portions. >>> >>> Thats what I can think of off the top of my head. You can find more >>> information about it here: >>> https://docs.djangoproject.com/en/dev/topics/cache/ >>> http://memcached.org/ >>> http://redis.io/ >>> >>> The main thing to remember is that both memcache and redis are in memory >>> databases (key-value store) (even though redis can be persisted) and if the >>> server is rebooted, then the cache is empty. Also being a in memory >>> database means that getting information back from the key-value store is >>> more or less instantanious especially if you compare to a standard sql >>> database. >>> >>> Regards, >>> >>> Andréas >>> >>> >>> 2014-03-01 21:27 GMT+01:00 Robin Lery <[email protected]>: >>> >>>> Use cases with memcached and redis please. >>>> >>>> >>>> On Sun, Mar 2, 2014 at 1:45 AM, Andreas Kuhne < >>>> [email protected]> wrote: >>>> >>>>> Hi again, >>>>> >>>>> Do you mean use cases with redis and memcache or with S3? >>>>> >>>>> Regards, >>>>> >>>>> Andréas >>>>> >>>>> 2014-03-01 21:00 GMT+01:00 Robin Lery <[email protected]>: >>>>> >>>>>> Hello, >>>>>> Thank you for your answer. Would you please elaborate a little more >>>>>> about the use cases with these? And can I use them together? >>>>>> >>>>>> Thank you. >>>>>> >>>>>> >>>>>> On Sun, Mar 2, 2014 at 1:01 AM, Andreas Kuhne < >>>>>> [email protected]> wrote: >>>>>> >>>>>>> Hi, >>>>>>> >>>>>>> In response to your question about memcache and redis, they are >>>>>>> extremely useful, if you use them correctly. For example if you are >>>>>>> generating a query to your database that takes 1 second to finish, and >>>>>>> you >>>>>>> cache the results in memcache or redis, then you would be able to get >>>>>>> the >>>>>>> second request down to 50 ms instead. Thats the difference in response >>>>>>> time. Redis and memcache are in memory databases and are extremely fast! >>>>>>> >>>>>>> Regarding your second question, if you need to store alot of >>>>>>> pictures and videos, I would use Amazon S3 with the django storages >>>>>>> backend >>>>>>> for S3. >>>>>>> >>>>>>> Regards, >>>>>>> >>>>>>> Andréas >>>>>>> >>>>>>> >>>>>>> 2014-03-01 17:28 GMT+01:00 Robin Lery <[email protected]>: >>>>>>> >>>>>>>> Hello, >>>>>>>> Another noob question. Please bear with me. I am really very >>>>>>>> confused between memcached and redis. I know they both are used for >>>>>>>> caching. But I don't know how much does they help. And lastly, I would >>>>>>>> like >>>>>>>> know what would you use for a site with users uploaded pictures and >>>>>>>> videos >>>>>>>> too? I hope I was clear. If not please ask. Your help and guidance >>>>>>>> will be >>>>>>>> very much appreciated. >>>>>>>> >>>>>>>> Thank you. >>>>>>>> Robin. >>>>>>>> >>>>>>>> -- >>>>>>>> You received this message because you are subscribed to the Google >>>>>>>> Groups "Django users" group. >>>>>>>> To unsubscribe from this group and stop receiving emails from it, >>>>>>>> send an email to [email protected]. >>>>>>>> To post to this group, send email to [email protected]. >>>>>>>> Visit this group at http://groups.google.com/group/django-users. >>>>>>>> To view this discussion on the web visit >>>>>>>> https://groups.google.com/d/msgid/django-users/CA%2B4-nGqoYH24%2BSLzM8Jx3dN_xiPFYpZ90-gqfRNVpcWUEK%3DVsw%40mail.gmail.com >>>>>>>> . >>>>>>>> For more options, visit https://groups.google.com/groups/opt_out. >>>>>>>> >>>>>>> >>>>>>> -- >>>>>>> You received this message because you are subscribed to the Google >>>>>>> Groups "Django users" group. >>>>>>> To unsubscribe from this group and stop receiving emails from it, >>>>>>> send an email to [email protected]. >>>>>>> To post to this group, send email to [email protected]. >>>>>>> Visit this group at http://groups.google.com/group/django-users. >>>>>>> To view this discussion on the web visit >>>>>>> https://groups.google.com/d/msgid/django-users/CALXYUbmmkXRQE8m92S7NncYg4BN18VCbhVm13hgUbYrq1H5B%3Dw%40mail.gmail.com >>>>>>> . >>>>>>> >>>>>>> For more options, visit https://groups.google.com/groups/opt_out. >>>>>>> >>>>>> >>>>>> -- >>>>>> You received this message because you are subscribed to the Google >>>>>> Groups "Django users" group. >>>>>> To unsubscribe from this group and stop receiving emails from it, >>>>>> send an email to [email protected]. >>>>>> To post to this group, send email to [email protected]. >>>>>> Visit this group at http://groups.google.com/group/django-users. >>>>>> To view this discussion on the web visit >>>>>> https://groups.google.com/d/msgid/django-users/CA%2B4-nGrHb_QH1YbXA4wOnW-nVJ-sVfTWfxUOxH%2Bvz%2BihxjC2XQ%40mail.gmail.com >>>>>> . >>>>>> >>>>>> For more options, visit https://groups.google.com/groups/opt_out. >>>>>> >>>>> >>>>> -- >>>>> You received this message because you are subscribed to the Google >>>>> Groups "Django users" group. >>>>> To unsubscribe from this group and stop receiving emails from it, send >>>>> an email to [email protected]. >>>>> To post to this group, send email to [email protected]. >>>>> Visit this group at http://groups.google.com/group/django-users. >>>>> To view this discussion on the web visit >>>>> https://groups.google.com/d/msgid/django-users/CALXYUbmBhXY%2BJcC2ghmL5%3DcEeMhjdnqj7XB3tWAacVxt99XBuw%40mail.gmail.com<https://groups.google.com/d/msgid/django-users/CALXYUbmBhXY%2BJcC2ghmL5%3DcEeMhjdnqj7XB3tWAacVxt99XBuw%40mail.gmail.com?utm_medium=email&utm_source=footer> >>>>> . >>>>> >>>>> For more options, visit https://groups.google.com/groups/opt_out. >>>>> >>>> >>>> -- >>>> You received this message because you are subscribed to the Google >>>> Groups "Django users" group. >>>> To unsubscribe from this group and stop receiving emails from it, send >>>> an email to [email protected]. >>>> To post to this group, send email to [email protected]. >>>> Visit this group at http://groups.google.com/group/django-users. >>>> To view this discussion on the web visit >>>> https://groups.google.com/d/msgid/django-users/CA%2B4-nGpmxLcJQignKqP%3DPK1h7V0n5-953mSF%3D%2Bd%3DE53w9P2xZQ%40mail.gmail.com<https://groups.google.com/d/msgid/django-users/CA%2B4-nGpmxLcJQignKqP%3DPK1h7V0n5-953mSF%3D%2Bd%3DE53w9P2xZQ%40mail.gmail.com?utm_medium=email&utm_source=footer> >>>> . >>>> >>>> For more options, visit https://groups.google.com/groups/opt_out. >>>> >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Django users" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected]. >>> To post to this group, send email to [email protected]. >>> Visit this group at http://groups.google.com/group/django-users. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/django-users/CALXYUbnvEbZ6%3DBh6s%2Bs8cVMofRu%3DiqFoQxA4e5RmfhdbGP7zaw%40mail.gmail.com<https://groups.google.com/d/msgid/django-users/CALXYUbnvEbZ6%3DBh6s%2Bs8cVMofRu%3DiqFoQxA4e5RmfhdbGP7zaw%40mail.gmail.com?utm_medium=email&utm_source=footer> >>> . >>> >>> For more options, visit https://groups.google.com/groups/opt_out. >>> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Django users" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> To post to this group, send email to [email protected]. >> Visit this group at http://groups.google.com/group/django-users. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/django-users/CA%2B4-nGpDyPeYfNubU_VHyMgyiNWC7e%2Br23fK5T72zjukAmxmuQ%40mail.gmail.com >> . >> >> For more options, visit https://groups.google.com/groups/opt_out. >> > > -- > You received this message because you are subscribed to the Google Groups > "Django users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/django-users. > To view this discussion on the web visit > https://groups.google.com/d/msgid/django-users/CALXYUbm4bLx709o79%2Bt1EOhMAdTPMZvKjgDaY8L%3DPjbvM96eAQ%40mail.gmail.com > . > > For more options, visit https://groups.google.com/groups/opt_out. > -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CA%2B4-nGr8jayi0Zn40_7bdzroWfFY3usHK1xdn%2BbswfrbDH3wrQ%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
