Apache 2.4.x Bandwidth Quota / Throttle / Speed - apache2

I'm looking for a new Apache 2.4.x module or solution which allows me to configure Bandwidth Quota's. Long ago I use mod_throttle which only works for 1.3 and is since no longer maintained. I've also been using mod_cband which I've patched to work with Apache 2.4 and it seems to be doing the job but I'm worried about future Apache upgrades could cause this software to become extinct as well. It also appears mod_cband is no longer maintained either.
I've looked at mod_bandwidth but that only appears to work for 1.3.x and mod_ratelimit doesn't exactly do what I'm looking for.
Specifically I'm looking for a way to set a max quota for each virtualhost and when that limit is reached either the connection is slowed down OR an error is displayed. Quota should be configured to automagically reset itself based on a pre-defined key, IE: 30 days, 2 hours, etc...
Any guidance would be nice. Paid software is ok for me too, long as I can demo it. Opensource solution would be best, of course =)
I should add, this should be for Unix/Linux, not Windows!

Try using this
http://dembol.org/blog/mod_cband
manges banwidth and qouta + works on linux

Related

Garbage Collection Setting Solr, sloe performance

We use a very old solr 4.2.0 system on OpenJDK6. I am battling a sloooowness issue on our system First I thought it was database, so we tuned all the queries. It did not help. Finally I tracked down to the Solr system performance that is causing the issue. It happens everyday exactly at the same time 8:58am CST, I see a spike in CPU usage and users feel slowness which is significant. And that happens to be the peak usage time with most of the surgeons on the system. I am in the process of migrating our system to a newer platform with Elasticsearch. In the meantime I need to keep this system going. I thought this is related to the GC on Solr. I know this is an age old topic discussed at length. What I see running on the system is the following command, with that what is my heap size, it has two switches Xmx128M and Xmx12500m, which take precedence? My machine has 32GB memory, I can bump this up if necessary. I am not sure where this 12500m is getting set. i looked at the /etc/init.d/tomcat6 script, it is set to 128M there. Not sure where this other setting is getting picked up from? We are on a Ubuntu system in AWS. Thanks for any help.
tomcat6 24483 17.3 44.7 19723020 13805172 ? Sl Apr13 3597:31 /usr/lib/jvm/java-6-openjdk/bin/java -Djava.util.logging.config.file=/var/lib/tomcat6/conf/logging.properties -Djava.awt.headless=true -Xmx128M -XX:+UseConcMarkSweepGC -Xms10000m -Xmx12500m -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager -Djava.endorsed.dirs=/usr/share/tomcat6/endorsed -classpath /usr/share/tomcat6/bin/bootstrap.jar -Dcatalina.base=/var/lib/tomcat6 -Dcatalina.home=/usr/share/tomcat6 -Djava.io.tmpdir=/tmp/tomcat6-tmp org.apache.catalina.startup.Bootstrap start

Joomla Site very slow

i'm struggling onto a problem that i can't find a way ti fix. I'm currently running joomla 3.4.5 and a gantry based theme. I tried minifying CSS, JS and HTML and also optimize the images with the google insight tool.
i've done a debug system and it shows that
Application: beforeRenderModule mod_rocknavmenu
implies 21.7 seconds ..... I think that is the issue .... how can i solve that?
The site is this
Thank you for your supoprt
I would guess the site is slow due to your hosting.
Also news01.png and news02.png are taking several seconds each to come through.
Update all of your extensions, out of date extensions can impact performance.
Check your slow query log, CPU, and memory usage on your server. Those will tell you more about potential issues.
Found realy easy solution - just disable System - Model plugin

Is the Meanstack suitable for production?

I have been looking at the various Meanstack frameworks out on the net - and whilst impressed with what they achieve I have one serious concern - the number of files used in a typical stack - meanstack.js uses over 15000 files whilst the bmean example has a modest 1900 in comparison.
The question I am asking myself is would I be happy to put my trust is such a system from a production view point - what happens when something goes wrong how easy is it going to be to find the answer? You can almost bet that when your most important customer logs on it is going to go haywire. Also what happens when Angular version 2 comes along it could require a complete rewrite but by then the stack your using has been customised and difficult to change?
Am I getting over concerned about the technology - my intended approach is to strip the client side code out of the bmean example and rewrite it with my own - at least that way I know (and control) what goes on in the client. Do you think this is the correct way to proceed?
With most systems there is a bit of preparation required before going to production. The same is true with mean.io (using multiple cpu's, improved aggregation, caching, etc etc)
The large number of files is essentially a product of the way npm handles dependencies. Each module is able to define independent versions of the same dependencies thus creating a bit of bloat but at the same time allowing a lot of flexability in nodejs code.
We currently have a number of mean.io projects in production phase and have been very happy with performance and the overall experience.
New releases of the project are scheduled every couple of months, upgrading should not be too much of a problem if you use the package system correctly.
Issues with the project are handled and managed through github issues additional support can be found on our irc (freenode #mean_io) channel as well as on facebook.
For commercial support have a look at the support page

GAE downloading log with LogQuery

My application generates many, many log messages. I would like to download only messages in a specific time interval. I looked around and LogQuery seems to be a good choice.
It seems like LogQuery, as specified here:
https://developers.google.com/appengine/docs/java/javadoc/com/google/appengine/api/log/LogQuery.Builder
, let one specify a start and end time in milliseconds.
However, there is no such method withStartTimeMillis or withEndTimeMillis in the GAE library that I downloaded from the web. I'm using GAE SDK 1.7.1. There are only withStartTimeUSec and withEndTimeUsec which deal in microsecond.
What's amiss here?
LogQuery.Builder has both methods: withStartTimeMillis(long startTimeMillis) and withStartTimeUsec(long startTimeUsec).
Also, the current version is 1.8.1, so you should upgrade to that before starting to resolve errors.

Upgrading Solr VM - could this cause problems?

I have a Solr installation running on JVM 1.6.0_18 and I would like to migrate into a much more powerful machine where it will share a 1.6.0_21 JVM with another application (Solr and the other application won't share the same Tomcat instance btw).
Will this pose any problems? Are the JVM requirements documented anywhere?
I think you will be fine. But if someone wants to upgrade it above 1.6.0_21, maybe you should go to 1.6.0_29 and not look back.
Because after _21 until _29, the code that lucene uses to read variable-length integers (used all the time in search!) is sometimes wrongly compiled by hotspot... we tried to add a hack/workaround (manually unroll it to dodge the bugs) but in general I would just avoid these versions, see https://issues.apache.org/jira/browse/LUCENE-2975
In response to your questions about "JVM requirements", lucene doesn't have "special" JVM requirements, only that we have lots of tests that actually execute things more than 10,000 times, and have found bugs in particular versions you should avoid, thats all.
As of posting this comment, I only know of minor issues with 1.6.0_29 and 1.7.0_01. So I would really recommend these as some major bugs previously affecting lucene are fixed there.

Resources