hi,
i do several test to learn where is the best place to store file.
e.g.
*result network time latency in chrome developer tools : 1 ms*
response.logo = IMG(_src=URL('static', 'images/logo.png'),
_width="20px", _title="logo", _class="brand")
*result network time latency in chrome developer tools : 65-75 ms (store in
table without uploadfield define)*
row = db(db.company.id == 1).select(cache = (cache.ram, 10)).first()
response.logo = IMG(_src=URL('download', args=row.logo),
_width="20px", _title=row.name, _class="brand")
*result network time latency in chrome developer tools : 70-80 ms (store in
table define uploadfield type blob)*
row = db(db.company.id == 1).select(cache = (cache.ram, 10)).first()
response.logo = IMG(_src=URL('download', args=row.logo),
_width="20px", _title=row.name, _class="brand")
base on that test i can assume that the file store in disk locally is
faster than the file that store in table (with or without uploadfield type
blob define)
my question is should i store all file in disk locally and then use img url
download to static images folder? what about something like image product,
that can be update, i think it's not efficient when store it in disk
manually. what is the best way for do that?
thanks and best regards,
stifan
--
Resources:
- http://web2py.com
- http://web2py.com/book (Documentation)
- http://github.com/web2py/web2py (Source code)
- https://code.google.com/p/web2py/issues/list (Report Issues)
---
You received this message because you are subscribed to the Google Groups
"web2py-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.