04-01-2014
There may be repeated rogue queries that are trying to return vast amounts of data. If the user is disconnected/timed out/gets bored, they may well re-issue. I would consider reading the application logs to check that the queries are indeed going to return suitable data volumes.
This was learned from prolonged painful experience eventually leading to better validation and sanity checking on the application server before the query was executed.
Robin
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hello, everyone:
i encounter a problem these days , pls help me ,thanks in advance.
my env:
machine: ES40 A ES40 B
os: true64 Unix 4.0f
note: src.tar 8M network card speed 100M
my problem:
... (3 Replies)
Discussion started by: q30
3 Replies
2. AIX
Hi,
I am trying to send oracle archives over WAN and it is taking hell a lot of time. To reduce the time, I tried to gzip the files and send over to the other side. That seems to reduce the time. Does anybody have experienced this kind of problem and any possible ways to reduce the time.
... (1 Reply)
Discussion started by: giribt
1 Replies
3. Solaris
At work, I'm in a Solaris environment working with csh, and $PATH is populated with anywhere between 10 and 20 entries.
Last week, every command I issued (even "ls") took several seconds, if not an entire minute, to run. Once I moved "/home/sybase/bin" to the end of $PATH, certain commands... (2 Replies)
Discussion started by: acheong87
2 Replies
4. Red Hat
hey guys,
We have two Sun x2100 servers running RHEL5 in a test environment. Both servers are fresh OS installs and hooked up to the same network switch.
When ssh'ing to one server, there is a significant delay, while ssh'ing to the other server, the connection is almost instant. We are... (2 Replies)
Discussion started by: amheck
2 Replies
5. BSD
hi
howto restart the network with a wireless interface including wpa_supplicant on freeBSD 7.2 without reboot? (3 Replies)
Discussion started by: ccc
3 Replies
6. AIX
Hi All,
Please let me know the command to restart the network interface and enable it on boot in AIX, similar to /etc/init.d/network restart in Redhat.
Thanks,
Sunil.K
please watch out to post in the right subforum! (9 Replies)
Discussion started by: sunilrk07
9 Replies
7. UNIX for Advanced & Expert Users
Hi Guys,
I've inherited a mess of an infrastructure in my new job, there hasn't been a sys admin in post for about a year, so things are falling apart. The first thing to break after I started was the printer server. I have it working again, and people can print, however it's very slow, slower... (0 Replies)
Discussion started by: rudigarude
0 Replies
8. Solaris
I have identical M5000 machines that are needing to transfer very large amounts of data between them. These are fully loaded machines, and I've already checked IO, memory usage, etc... I get poor network performance even when the machines are idle or copying via loopback. The 10 GB NICs are... (7 Replies)
Discussion started by: christr
7 Replies
9. AIX
Hello everyone,
I've been a life long Unix/Linux user but I'll be the first to admit I have little specific AIX knowledge at this point and I've inherited these systems for better or worse so please forgive if I ask something in the wrong context. And yes, I've searched google for 3 days now :)... (3 Replies)
Discussion started by: BDMcGrew
3 Replies
10. Debian
Hello,
I would like to do follow steps.
Set a static IP-Adress on eth0 (For Testing)
Set DHCP on eth0
All steps should be done without a single reboot.
/etc/network/interfaces
iface eth0 inet static
address 192.0.2.7/24
gateway 192.0.2.254How do i perform... (3 Replies)
Discussion started by: int3g3r
3 Replies
LEARN ABOUT DEBIAN
jifty::plugin::sqlqueries
Jifty::Plugin::SQLQueries(3pm) User Contributed Perl Documentation Jifty::Plugin::SQLQueries(3pm)
NAME
Jifty::Plugin::SQLQueries - Inspect your application's SQL queries
DESCRIPTION
This plugin will log each SQL query, its duration, its bind parameters, and its stack trace. Such reports are available at:
http://your.app/__jifty/admin/requests
USAGE
Add the following to your site_config.yml
framework:
Plugins:
- SQLQueries: {}
You can turn on and off the stacktrace, as well as an "EXPLAIN" of each query, using options to the plugin:
framework:
Plugins:
- SQLQueries:
stacktrace: 0
explain: 1
The plugin defaults to logging the stack trace, but not the explain.
METHODS
init
Sets up a "post_init" hook.
inspect_before_request
Clears the query log so we don't log any unrelated previous queries.
inspect_after_request
Stash the query log.
inspect_render_summary
Display how many queries and their total time.
inspect_render_analysis
Render a template with all the detailed information.
post_init
Tells Jifty::DBI to log queries in a way that records stack traces.
prereq_plugins
This plugin depends on Jifty::Plugin::RequestInspector.
COPYRIGHT AND LICENSE
Copyright 2007-2010 Best Practical Solutions
This is free software and may be modified and distributed under the same terms as Perl itself.
perl v5.14.2 2010-12-10 Jifty::Plugin::SQLQueries(3pm)