Forum Activity for @soaringeagle

soaringeagle
@soaringeagle
03/23/18 02:16:29PM
3,304 posts

profile domains and litespeed


Using Jamroom

got it working
just all the experts say linux never needs to be rebooted, but that was all it took
which is what i thought
reloading apache conf doesnt do it

and really thought you had
its alot quicker and less cpu intensive

you should do some side by side performance tests jamroom likes litespeed
soaringeagle
@soaringeagle
03/22/18 09:08:22PM
3,304 posts

profile domains and litespeed


Using Jamroom

i believe brian has alot
soaringeagle
@soaringeagle
03/22/18 08:04:01PM
3,304 posts

profile domains and litespeed


Using Jamroom

having a lil trouble getting profile domains functioning on litespeed (503 service unavailable)
not sure where exactly to include the includeoptional (i use plesk as well i added it to apache ningx config which seemed right)
i do not use nignx i know profile domains does not work with it

i do however have susexec php enabled for user home space only
i was old its not best to use susexec php however
when disabling it i get "invalid media url' on all uploaded videos and i assume music

profile domains is the last thing i need to get working correctly
just to be thourough
dns should use same ip as the main site ip right even if the site uses an ssl ip and you dont have ssl enabled on profile domains? or should they use the shared ip i think i tried both

edit:
teted in apache both profile domains redirect to the main dreadlockssite.com page not the profiles
but no 503
however i think its still redirectinginncorectly

updated by @soaringeagle: 06/23/18 05:54:24PM
soaringeagle
@soaringeagle
03/22/18 07:57:44PM
3,304 posts

performance test additional test


Suggestions

pingdom tools is a help..to a point
i guess what im getting at is apache vs litespeed vs diferent configuration options php settings php handlers etc can have a big impact on performance , cpu loads, wait times etc
database does always seem to be the toughest thing to tune
i can't get to baseline (6.5) and hover around 8.5 ish

on that note
table_open_cache
gives conflicting info on optimization
while set at 2424 it suggests increasing it but at the same time says increasing it above 64 can have a big performance issue and its best to keep it below 64

whats your thoughts on that?
soaringeagle
@soaringeagle
03/21/18 11:14:56AM
3,304 posts

performance test additional test


Suggestions

the cpu test tests
Processor Test • The Processor Test runs a series of calculations on your server processor (CPU) to see how quickly it can finish. Processor speed is important as it determines how quickly the Jamroom PHP code can be executed.


but we also need for performance consideration how quickly the actual php code is executed and served by the webserver over the network
updated by @soaringeagle: 06/23/18 09:23:27AM
soaringeagle
@soaringeagle
03/11/18 09:47:20AM
3,304 posts

redis ram


Using Jamroom

thats what i assumed just wanted to be sure

1 other question i was told not to use susexec php in litespeed but without it i get those cannot load media url errors only when i select users home direcory only do videos (and music i assume but didnt test) that play right
soaringeagle
@soaringeagle
03/10/18 07:30:41PM
3,304 posts

redis ram


Using Jamroom

is there any drawbacks to giving redis extra ram to work with if its using all you allocated (2 gb)
large number are expire keys so is it worth keeping them cached for hit rate improvement or won't it hit them if they are expired
would adding more ram allocation increase hit rate?

note also the other day when trying to fix redis sessions we had out of control cpu use
did some redis tweaking that did not fix the sessions but really improved how it runs drasticly
and
fixed the video uploading and ffmpeg not converting issue i have had or a pretty long time..like a year or more


this is what i see
i know how she runs i could go to 4 gb with ease
but should would it improve the hit rate or just use ram for expired useless kys
redis.jpg redis.jpg - 30KB

updated by @soaringeagle: 06/19/18 12:54:15AM
soaringeagle
@soaringeagle
03/05/18 09:17:34AM
3,304 posts

cometchat & php versions


Using Jamroom

firewall wasnt even installed i installed it allowed 2 way communication with port
still
yea mysql sessions it is. it works great as a data cache though
soaringeagle
@soaringeagle
03/05/18 08:57:24AM
3,304 posts

cometchat & php versions


Using Jamroom

ok switched back to that (3.2.1 is my version)
but changed bind
issue still remains
soaringeagle
@soaringeagle
03/05/18 08:51:22AM
3,304 posts

cometchat & php versions


Using Jamroom

starting from this
http://download.redis.io/redis-stable/redis.conf
i got a few eerrors and had to comment out those lines
but end result was bind address in use

[root@server ~]# redis-server /etc/myredis.conf

*** FATAL CONFIG FILE ERROR ***
Reading the configuration file, at line 194
>>> 'always-show-logo yes'
Bad directive or wrong number of arguments
[root@server ~]# nano /etc/myredis.conf
[root@server ~]# redis-server /etc/myredis.conf

*** FATAL CONFIG FILE ERROR ***
Reading the configuration file, at line 647
>>> 'lazyfree-lazy-eviction no'
Bad directive or wrong number of arguments
[root@server ~]# nano /etc/myredis.conf
[root@server ~]# redis-server /etc/myredis.conf

*** FATAL CONFIG FILE ERROR ***
Reading the configuration file, at line 782
>>> 'aof-use-rdb-preamble no'
Bad directive or wrong number of arguments
[root@server ~]# nano /etc/myredis.conf
[root@server ~]# redis-server /etc/myredis.conf
9889:M 05 Mar 10:43:57.030 * Increased maximum number of open files to 10032 (it was originally set to 1024).
9889:M 05 Mar 10:43:57.030 # Creating Server TCP listening socket 127.0.0.1:6379: bind: Address already in use
[root@server ~]# nano /etc/myredis.conf
[root@server ~]# redis-server /etc/myredis.conf
10482:M 05 Mar 10:48:07.266 * Increased maximum number of open files to 10032 (it was originally set to 1024).
10482:M 05 Mar 10:48:07.266 # Creating Server TCP listening socket 127.0.0.1:6379: bind: Address already in use
[root@server ~]#
  28