Help! Подвисают страницы при рефреше
Help! Подвисают страницы при рефреше
Заметил такую особенность, иногда когда в шаблонах меняешь хтмл код, потом обновляешь страницу в браузере она подвисает, загрузка может достигать 7-10 секунд. Последующие рефреши идут на ура пока опять что-нибудь не изменишь в коде. Закономерности 100-процентной вывести не смог. Пробовал любые сайты на локалхосте, и Yii и не Yii
Железо на компе очень шустрое.
Есть мысли из-за чего такое может быть?
система Win8, Apache 2.4.9 php 5.5.13 MySQL Server 5.6
Железо на компе очень шустрое.
Есть мысли из-за чего такое может быть?
система Win8, Apache 2.4.9 php 5.5.13 MySQL Server 5.6
ភាសាខ្មែរ Yii2 - это кайф!
- samdark
- Администратор
- Сообщения: 9489
- Зарегистрирован: 2009.04.02, 13:46
- Откуда: Воронеж
- Контактная информация:
Re: Help! Подвисают страницы при рефреше
View идёт без всякого кеша, на диск ничего вроде не пишется. Если у вас там не 100500 реквестов на страницу, ищите в настройках Apache, PHP и т.д.
Нравится Yii? Давайте сделаем его лучше!.
-
- Сообщения: 1428
- Зарегистрирован: 2009.08.20, 22:54
- Откуда: Молдова, Бельцы
- Контактная информация:
Re: Help! Подвисают страницы при рефреше
Может жесткий тупит ?
Re: Help! Подвисают страницы при рефреше
Нет, винт SSD новый, проблем нет.
2 Sam Dark, я не про Yii, зависает в любых скриптах, сайтах cms
Подозрение на MySQL. Бывает открываю phpMyAdmin и он так же тупит
Гляньте мой My.ini может там косяк есть.
2 Sam Dark, я не про Yii, зависает в любых скриптах, сайтах cms
Подозрение на MySQL. Бывает открываю phpMyAdmin и он так же тупит
Гляньте мой My.ini может там косяк есть.
Код: Выделить всё
# The TCP/IP Port the MySQL Server will listen on
port=3306
# Path to installation directory. All paths are usually resolved relative to this.
# basedir="D:/Program Files/MySQL/MySQL Server 5.6/"
# Path to the database root
datadir="D:/Program Files/MySQL/data\"
# The default character set that will be used when a new schema or table is
# created and no character set is defined
character-set-server=utf8
# The default storage engine that will be used when create new tables when
default-storage-engine=INNODB
# Set the SQL mode to strict
sql-mode=""
# Enable Windows Authentication
# plugin-load=authentication_windows.dll
# General and Slow logging.
log-output=FILE
general-log=0
general_log_file="PC.log"
slow-query-log=1
slow_query_log_file="PC-slow.log"
long_query_time=10
# Binary Logging.
# log-bin
# Error Logging.
log-error="PC.err"
# The maximum amount of concurrent sessions the MySQL server will
# allow. One of these connections will be reserved for a user with
# SUPER privileges to allow the administrator to login even if the
# connection limit has been reached.
max_connections=151
# Query cache is used to cache SELECT results and later return them
# without actual executing the same query once again. Having the query
# cache enabled may result in significant speed improvements, if your
# have a lot of identical queries and rarely changing tables. See the
# "Qcache_lowmem_prunes" status variable to check if the current value
# is high enough for your load.
# Note: In case your tables change very often or if your queries are
# textually different every time, the query cache may result in a
# slowdown instead of a performance improvement.
query_cache_size=1M
# The number of open tables for all threads. Increasing this value
# increases the number of file descriptors that mysqld requires.
# Therefore you have to make sure to set the amount of open files
# allowed to at least 4096 in the variable "open-files-limit" in
# section [mysqld_safe]
table_open_cache=2000
# Maximum size for internal (in-memory) temporary tables. If a table
# grows larger than this value, it is automatically converted to disk
# based table This limitation is for a single table. There can be many
# of them.
tmp_table_size=9M
# How many threads we should keep in a cache for reuse. When a client
# disconnects, the client's threads are put in the cache if there aren't
# more than thread_cache_size threads from before. This greatly reduces
# the amount of thread creations needed if you have a lot of new
# connections. (Normally this doesn't give a notable performance
# improvement if you have a good thread implementation.)
thread_cache_size=10
#*** MyISAM Specific options
# The maximum size of the temporary file MySQL is allowed to use while
# recreating the index (during REPAIR, ALTER TABLE or LOAD DATA INFILE.
# If the file-size would be bigger than this, the index will be created
# through the key cache (which is slower).
myisam_max_sort_file_size=100G
# If the temporary file used for fast index creation would be bigger
# than using the key cache by the amount specified here, then prefer the
# key cache method. This is mainly used to force long character keys in
# large tables to use the slower key cache method to create the index.
myisam_sort_buffer_size=10M
# Size of the Key Buffer, used to cache index blocks for MyISAM tables.
# Do not set it larger than 30% of your available memory, as some memory
# is also required by the OS to cache rows. Even if you're not using
# MyISAM tables, you should still set it to 8-64M as it will also be
# used for internal temporary disk tables.
key_buffer_size=80M
# Size of the buffer used for doing full table scans of MyISAM tables.
# Allocated per thread, if a full scan is needed.
read_buffer_size=190K
read_rnd_buffer_size=2560K
# This buffer is allocated when MySQL needs to rebuild the index in
# REPAIR, OPTIMZE, ALTER table statements as well as in LOAD DATA INFILE
# into an empty table. It is allocated per thread so be careful with
# large settings.
sort_buffer_size=256K
#*** INNODB Specific options ***
# innodb_data_home_dir=0.0
# Use this option if you have a MySQL server with InnoDB support enabled
# but you do not plan to use it. This will save memory and disk space
# and speed up some things.
# skip-innodb
# Additional memory pool that is used by InnoDB to store metadata
# information. If InnoDB requires more memory for this purpose it will
# start to allocate it from the OS. As this is fast enough on most
# recent operating systems, you normally do not need to change this
# value. SHOW INNODB STATUS will display the current amount used.
innodb_additional_mem_pool_size=2M
# If set to 1, InnoDB will flush (fsync) the transaction logs to the
# disk at each commit, which offers full ACID behavior. If you are
# willing to compromise this safety, and you are running small
# transactions, you may set this to 0 or 2 to reduce disk I/O to the
# logs. Value 0 means that the log is only written to the log file and
# the log file flushed to disk approximately once per second. Value 2
# means the log is written to the log file at each commit, but the log
# file is only flushed to disk approximately once per second.
innodb_flush_log_at_trx_commit=1
# The size of the buffer InnoDB uses for buffering log data. As soon as
# it is full, InnoDB will have to flush it to disk. As it is flushed
# once per second anyway, it does not make sense to have it very large
# (even with long transactions).
innodb_log_buffer_size=1M
# InnoDB, unlike MyISAM, uses a buffer pool to cache both indexes and
# row data. The bigger you set this the less disk I/O is needed to
# access data in tables. On a dedicated database server you may set this
# parameter up to 80% of the machine physical memory size. Do not set it
# too large, though, because competition of the physical memory may
# cause paging in the operating system. Note that on 32bit systems you
# might be limited to 2-3.5G of user level memory per process, so do not
# set it too high.
innodb_buffer_pool_size=13M
# Size of each log file in a log group. You should set the combined size
# of log files to about 25%-100% of your buffer pool size to avoid
# unneeded buffer pool flush activity on log file overwrite. However,
# note that a larger logfile size will increase the time needed for the
# recovery process.
innodb_log_file_size=48M
# Number of threads allowed inside the InnoDB kernel. The optimal value
# depends highly on the application, hardware as well as the OS
# scheduler properties. A too high value may lead to thread thrashing.
innodb_thread_concurrency=8
# The increment size (in MB) for extending the size of an auto-extend InnoDB system tablespace file when it becomes full.
innodb_autoextend_increment=64
# The number of regions that the InnoDB buffer pool is divided into.
# For systems with buffer pools in the multi-gigabyte range, dividing the buffer pool into separate instances can improve concurrency,
# by reducing contention as different threads read and write to cached pages.
innodb_buffer_pool_instances=8
# Determines the number of threads that can enter InnoDB concurrently.
innodb_concurrency_tickets=5000
# Specifies how long in milliseconds (ms) a block inserted into the old sublist must stay there after its first access before
# it can be moved to the new sublist.
innodb_old_blocks_time=1000
# It specifies the maximum number of .ibd files that MySQL can keep open at one time. The minimum value is 10.
# innodb_open_files
# When this variable is enabled, InnoDB updates statistics during metadata statements.
innodb_stats_on_metadata=0
# When innodb_file_per_table is enabled (the default in 5.6.6 and higher), InnoDB stores the data and indexes for each newly created table
# in a separate .ibd file, rather than in the system tablespace.
innodb_file_per_table=1
# Use the following list of values: 0 for crc32, 1 for strict_crc32, 2 for innodb, 3 for strict_innodb, 4 for none, 5 for strict_none.
innodb_checksum_algorithm=0
# The number of outstanding connection requests MySQL can have.
# This option is useful when the main MySQL thread gets many connection requests in a very short time.
# It then takes some time (although very little) for the main thread to check the connection and start a new thread.
# The back_log value indicates how many requests can be stacked during this short time before MySQL momentarily
# stops answering new requests.
# You need to increase this only if you expect a large number of connections in a short period of time.
back_log=80
# If this is set to a nonzero value, all tables are closed every flush_time seconds to free up resources and
# synchronize unflushed data to disk.
# This option is best used only on systems with minimal resources.
flush_time=0
# The minimum size of the buffer that is used for plain index scans, range index scans, and joins that do not use
# indexes and thus perform full table scans.
join_buffer_size=256K
# The maximum size of one packet or any generated or intermediate string, or any parameter sent by the
# mysql_stmt_send_long_data() C API function.
max_allowed_packet=4M
# If more than this many successive connection requests from a host are interrupted without a successful connection,
# the server blocks that host from performing further connections.
max_connect_errors=100
# Changes the number of file descriptors available to mysqld.
# You should try increasing the value of this option if mysqld gives you the error "Too many open files".
open_files_limit=4161
# Set the query cache type. 0 for OFF, 1 for ON and 2 for DEMAND.
query_cache_type=1
# If you see many sort_merge_passes per second in SHOW GLOBAL STATUS output, you can consider increasing the
# sort_buffer_size value to speed up ORDER BY or GROUP BY operations that cannot be improved with query optimization
# or improved indexing.
sort_buffer_size=256K
# The number of table definitions (from .frm files) that can be stored in the definition cache.
# If you use a large number of tables, you can create a large table definition cache to speed up opening of tables.
# The table definition cache takes less space and does not use file descriptors, unlike the normal table cache.
# The minimum and default values are both 400.
table_definition_cache=1400
# Specify the maximum size of a row-based binary log event, in bytes.
# Rows are grouped into events smaller than this size if possible. The value should be a multiple of 256.
binlog_row_event_max_size=8K
# If the value of this variable is greater than 0, a replication slave synchronizes its master.info file to disk.
# (using fdatasync()) after every sync_master_info events.
sync_master_info=10000
# If the value of this variable is greater than 0, the MySQL server synchronizes its relay log to disk.
# (using fdatasync()) after every sync_relay_log writes to the relay log.
sync_relay_log=10000
# If the value of this variable is greater than 0, a replication slave synchronizes its relay-log.info file to disk.
# (using fdatasync()) after every sync_relay_log_info transactions.
sync_relay_log_info=10000
ភាសាខ្មែរ Yii2 - это кайф!
Re: Help! Подвисают страницы при рефреше
И не MySQL, осталось смотреть Apache и php
ភាសាខ្មែរ Yii2 - это кайф!
Re: Help! Подвисают страницы при рефреше
может вообще сам браузер глючит? попробовать на другом или кеш почистить на текущем
Re: Help! Подвисают страницы при рефреше
То что он новый, это не даёт 100% вероятности в его исправности. Тоже вариант прогнать тестами егоAkulenok писал(а):Нет, винт SSD новый, проблем нет.
Re: Help! Подвисают страницы при рефреше
это же ссд, он сам все делает и распредиляет
Re: Help! Подвисают страницы при рефреше
Браузеры конечно пробовал менять, не помогло
винт тоже проверял, никаких проблем.
Сейчас второй осью линух хочу поставить, посмотрим как там будет.
винт тоже проверял, никаких проблем.
Сейчас второй осью линух хочу поставить, посмотрим как там будет.
ភាសាខ្មែរ Yii2 - это кайф!
-
- Сообщения: 1428
- Зарегистрирован: 2009.08.20, 22:54
- Откуда: Молдова, Бельцы
- Контактная информация:
Re: Help! Подвисают страницы при рефреше
Может из-за сессий ? Так бывает, sam об этом в блоге еще писал.
Re: Help! Подвисают страницы при рефреше
Страница тормозит и без сессий, просто тестировал скрипт обычный не большой цикл.
странность в том что тормоза не всегда, при первых пяти рефрешах может быть все норм а потом шестой раз и тупняк.
Может быть из-за настроек сетки? NAT etc...
в httpd.conf менял ServerName убирал ставил, делал и localhost и 127.0.0.1 и в хостс тоже самое ставил и дефолтные конфиги пробовал.
ps: пока писал этот пост постоянно дергал страницы сайтов своих по F5 и надо же, ни одного зависона о_0
лог при запуске апача
вроде ничего криминального
странность в том что тормоза не всегда, при первых пяти рефрешах может быть все норм а потом шестой раз и тупняк.
Может быть из-за настроек сетки? NAT etc...
в httpd.conf менял ServerName убирал ставил, делал и localhost и 127.0.0.1 и в хостс тоже самое ставил и дефолтные конфиги пробовал.
ps: пока писал этот пост постоянно дергал страницы сайтов своих по F5 и надо же, ни одного зависона о_0
лог при запуске апача
Код: Выделить всё
[Tue Aug 19 23:45:21.890434 2014] [mpm_winnt:notice] [pid 1208:tid 456] AH00424: Parent: Received restart signal -- Restarting the server.
[Tue Aug 19 23:45:21.904462 2014] [core:warn] [pid 1208:tid 456] AH00117: Ignoring deprecated use of DefaultType in line 188 of D:/Program Files/Apache/conf/httpd.conf.
[Tue Aug 19 23:45:21.944501 2014] [mpm_winnt:notice] [pid 1208:tid 456] AH00455: Apache/2.4.9 (Win64) configured -- resuming normal operations
[Tue Aug 19 23:45:21.945503 2014] [mpm_winnt:notice] [pid 1208:tid 456] AH00456: Apache Lounge VC11 Server built: Mar 16 2014 12:42:59
[Tue Aug 19 23:45:21.945503 2014] [core:notice] [pid 1208:tid 456] AH00094: Command line: 'D:\\Program Files\\Apache\\bin\\httpd.exe -d D:/Program Files/Apache'
[Tue Aug 19 23:45:21.946503 2014] [mpm_winnt:notice] [pid 1208:tid 456] AH00418: Parent: Created child process 2696
[Tue Aug 19 23:45:22.131735 2014] [core:warn] [pid 2696:tid 320] AH00117: Ignoring deprecated use of DefaultType in line 188 of D:/Program Files/Apache/conf/httpd.conf.
[Tue Aug 19 23:45:22.236880 2014] [core:warn] [pid 2696:tid 320] AH00117: Ignoring deprecated use of DefaultType in line 188 of D:/Program Files/Apache/conf/httpd.conf.
[Tue Aug 19 23:45:22.891696 2014] [mpm_winnt:notice] [pid 2696:tid 320] AH00354: Child: Starting 64 worker threads.
[Tue Aug 19 23:45:23.891945 2014] [mpm_winnt:notice] [pid 3440:tid 320] AH00364: Child: All worker threads have exited.
ភាសាខ្មែរ Yii2 - это кайф!
Re: Help! Подвисают страницы при рефреше
Нашел время и все таки установил linux-mint, проинсталиил apache+php+mysql
и никаких подвисаний нет! все как часы, четко быстро.
На винде полностью сносил MySQL , поставил новый, добавил всего одну базу и все равно тормозит.
Я просто уже хз из-за чего может быть такое, хоть винду сноси (
и никаких подвисаний нет! все как часы, четко быстро.
На винде полностью сносил MySQL , поставил новый, добавил всего одну базу и все равно тормозит.
Я просто уже хз из-за чего может быть такое, хоть винду сноси (
ភាសាខ្មែរ Yii2 - это кайф!
-
- Сообщения: 1
- Зарегистрирован: 2014.09.22, 08:27
- Откуда: Россия Москва
- Контактная информация:
Re: Help! Подвисают страницы при рефреше
Если у вас там не 100500 реквестов на страницу, ищите в настройках Apache, PHP и т.д.