[U2] Question on Unidata tables access speeds
Hi , Project data warehouse, Sources are Unidata tables, tool Datastage. Performance issue, while dumping in to hash file(Allowing stage write cash). It is searching 5.5 million rows and fetching 2.6 million rows and taking 2.5 hours. There is only one key column in the ouput. When I remove select caluse(I mean select all rows) and put that filter in my tool, it is ok, but not great. After that When I run parallel jobs , I mean select the data by 4 jobs for different ranges(all at the same time), it is taking 4 times than normal time . In other words, I am not getting performance like Oracle or other data bases. I am new to Unidata, is there any method where I can get good access speeds on Unidata.Any help will be highly appreciated. thanks pbr -- Electronic Privacy Notice. This e-mail, and any attachments, contains information that is, or may be, covered by the Electronic Communications Privacy Act, 18 U.S.C. 2510-2521, and is also confidential and proprietary in nature. If you are not the intended recipient, please be advised that you are legally prohibited from retaining, using, copying, distributing, or otherwise disclosing this information in any manner. Instead, please reply to the sender that you have received this communication in error, and then immediately delete it. Thank you in advance for your cooperation. == --- u2-users mailing list [EMAIL PROTECTED] To unsubscribe please visit http://listserver.u2ug.org/
[U2] B2B
Posted for non-member (Colin Lucas (The System Works) [EMAIL PROTECTED]). We are trying to test a secure B2B solution from within UV (version 10.0.8 on Unix variant TRU64 5.1b on an Alphaserver ES80) using XML https. The internet connection is via a proxy server that only listens for client connections on port 80. I have used setHTTPDefault to set the address of the proxy server and the port to 80; amongst other things. However, when I use submitRequest with a request handle created by a call to createSecureRequest it is directed to port 443 (SSL) of the proxy server. I have been able to determine this by using protocol logging and inspecting httplog. Normal http(80) through the proxy server is not a problem. Short of re-inventing the wheel and using the direct sockets API, can anybody shed some light on how to stop submitRequest when seeing https, deciding it must go to port 443 of the proxy. Unfortunately, due to some corporate constraints, changing the ports the proxy server listens on is not a trivial task. Thanks, Colin Lucas The System Works - Guaranteed ABN 49 010 514 557 Tel: + 61 7 3394 Fax: + 61 7 3394 0099 mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] The System Works Pty Ltd - Confidential Communication The information contained in this email is confidential. Any views or opinions expressed in this communication are those of the individual sender, except where the sender specifically states that the views or opinions are those of The System Works Pty Ltd. This communication is intended to be solely for the use of the addressee(s) and may contain copyright and / or legally privileged information. If you receive this email by mistake please promptly inform us by reply e-mail or telephone (+61 7 3394 ) and then delete the email and destroy any printed copy. Any unauthorised form or reproduction of this message is prohibited. As Internet communications are capable of data corruption, The System Works Pty Ltd does not guarantee the security of any information electronically transmitted and does not accept responsibility for any improper or incomplete transmission of the information contained in this communication, nor for any delay in its receipt. --- u2-users mailing list [EMAIL PROTECTED] To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] B2B
Secure implies SSL, which as you identify means using well known ports. I'd think it would take a lot more work to bastardise a solution using encrypted traffic on non-standard ports (I don't think you want to encrypt ALL traffic, so 80 won't do the trick) than changing your proxy to include SSL ports Ross Ferris Stamina Software Visage an Evolution in Software Development -Original Message- From: [EMAIL PROTECTED] [mailto:owner-u2- [EMAIL PROTECTED] On Behalf Of Moderator Sent: Monday, 9 August 2004 10:28 AM To: U2 Users Discussion List Subject: [U2] B2B Posted for non-member (Colin Lucas (The System Works) [EMAIL PROTECTED]). We are trying to test a secure B2B solution from within UV (version 10.0.8 on Unix variant TRU64 5.1b on an Alphaserver ES80) using XML https. The internet connection is via a proxy server that only listens for client connections on port 80. I have used setHTTPDefault to set the address of the proxy server and the port to 80; amongst other things. However, when I use submitRequest with a request handle created by a call to createSecureRequest it is directed to port 443 (SSL) of the proxy server. I have been able to determine this by using protocol logging and inspecting httplog. Normal http(80) through the proxy server is not a problem. Short of re-inventing the wheel and using the direct sockets API, can anybody shed some light on how to stop submitRequest when seeing https, deciding it must go to port 443 of the proxy. Unfortunately, due to some corporate constraints, changing the ports the proxy server listens on is not a trivial task. Thanks, Colin Lucas The System Works - Guaranteed ABN 49 010 514 557 Tel: + 61 7 3394 Fax: + 61 7 3394 0099 mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] The System Works Pty Ltd - Confidential Communication The information contained in this email is confidential. Any views or opinions expressed in this communication are those of the individual sender, except where the sender specifically states that the views or opinions are those of The System Works Pty Ltd. This communication is intended to be solely for the use of the addressee(s) and may contain copyright and / or legally privileged information. If you receive this email by mistake please promptly inform us by reply e-mail or telephone (+61 7 3394 ) and then delete the email and destroy any printed copy. Any unauthorised form or reproduction of this message is prohibited. As Internet communications are capable of data corruption, The System Works Pty Ltd does not guarantee the security of any information electronically transmitted and does not accept responsibility for any improper or incomplete transmission of the information contained in this communication, nor for any delay in its receipt. --- u2-users mailing list [EMAIL PROTECTED] To unsubscribe please visit http://listserver.u2ug.org/ --- Incoming mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.735 / Virus Database: 489 - Release Date: 6/08/2004 --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.735 / Virus Database: 489 - Release Date: 6/08/2004 --- u2-users mailing list [EMAIL PROTECTED] To unsubscribe please visit http://listserver.u2ug.org/
