MySQL Forums
Forum List  »  Newbie

Re: Use of memory table vs temporary table question
Posted by: Jorge Torralba
Date: January 24, 2011 11:14PM

Well, the way it is set up now is kind of poor here is the flow in more detail.

1. search for photos
2. return ALL rows (not just the 12) into a results table.
3. display the 12 rows per page. (thumbnails)
4. click on a thumb.
5. View full size and browse next and previous using data in results table.
6. If you click on search again, empty your previous results.

The reason I came up with results table was to preserve the query and let user browse all photos based on query.

I have an index on sessionid and timestamp. My concern is that this table will get too big when many people are searching.

You mention:

"Normally, one would store the data relevant to the user without storing the actual resultset"

How do you suggest I do that? This sounds like a good problem to solve :)

Also, forgot to mention tables are INNODB no MyISAM.

Here are my very basic my.cnf settings

#innodb_buffer_pool_size=2M
innodb_buffer_pool_size=1G
#innodb_additional_mem_pool_size=500K
innodb_additional_mem_pool_size=1M
#innodb_log_buffer_size=500K
innodb_log_buffer_size=1M
#innodb_thread_concurrency=2
innodb_thread_concurrency=5
max_connections=1000
table_cache=1000
thread_cache_size=40
thread_stack=100K
wait_timeout=20
connect_timeout=10
join_buffer=4M
myisam_sort_buffer_size=8M
query_cache_type=1
query_cache_size=10M
query_cache_limit=10M
read_rnd_buffer_size=4M
key_buffer_size=750M

Thanks,

JT

Options: ReplyQuote


Subject
Written By
Posted
Re: Use of memory table vs temporary table question
January 24, 2011 11:14PM


Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.